Hey @ampproject/wg-caching, these files were changed:

• extensions/amp-list/0.1/test/validator-amp-list.html
• extensions/amp-list/0.1/test/validator-amp-list.out
• extensions/amp-list/validator-amp-list.protoascii

@lannka have these been verified to not be in use? otherwise we need an i2d.

@samouri correct me. seems like it's a new feature that is not launched / announced yet?

Poll!
React with a 👍 if you like this name change and 👎 if you preferred strip-prefix

The reason I prefer xssi-prefix is that it explains itself.
strip-prefix only explains its behavior, which I felt is too generic. That is not how we normally write a config.

To back up my argument, I give a real world analogy

If a frying pan is configurable, this will be a more readable config to regular users:

nonSticky: true

instead of

coatWithTeflon: true

@lannka: I tend to agree with you, as long as xssi-prefix would never have a different use

Yeah, lets do it this way. @jridgewell / @lannka: if you have the chance can you submit this? I still don't have merge access.

I think either name is fine, but I actually read nonSticky as mapping to stripPrefix since they're less specific. :)

@choumx my bad try :-(

It might be more like a frying pan that was specifically meant for eggs, but could technically cook anything. Would you want your frying pan to have the function cookFood or cookEggs?