♻️ Conformance check allowlist#28778
Conversation
|
Hey @jeffkaufman! These files were changed: Hey @gmajoulet, @newmuis, @Enriqe! These files were changed: Hey @ampproject/wg-caching! These files were changed: |
jridgewell
left a comment
There was a problem hiding this comment.
Everything else LGTM.
| /** @const @enum {string} */ | ||
| export const Action = { | ||
| ADD_TO_ACTIONS_WHITELIST: 'addToActionsWhitelist', | ||
| ADD_TO_ACTIONS_ALLOWLIST: 'addToActionsAllowlist', |
There was a problem hiding this comment.
Changes to this file need @ampproject/wg-stories approval. I can't verify if this enum string is leaked to external code, or if this is truly internal.
There was a problem hiding this comment.
Adding a @ampproject/wg-stories member (@gmajoulet) to review.
caroqliu
left a comment
There was a problem hiding this comment.
LGTM, but needs a global replace for "a allowlist" to "an allowlist"
test/unit/test-batched-json.js
Outdated
| urlReplacements = { | ||
| expandUrlAsync: window.sandbox.stub(), | ||
| collectUnwhitelistedVarsSync: window.sandbox.stub(), | ||
| collectUnallowlistedVarsSync: window.sandbox.stub(), |
There was a problem hiding this comment.
Doesn't have to be addressed now but it's worth noting there is some inconsistency throughout with regards to "unallowlisted" versus "nonallowlisted"
|
This pull request introduces 1 alert when merging c1df0ad into 2121908 - view on LGTM.com new alerts:
|
|
|
||
| The AMP-Consent extension provides publishers the ability to collect and store a user's consent through a UI control, while also providing the ability to block other AMP components based on the user's consent. See [here for documentation](https://github.com/ampproject/amphtml/blob/master/extensions/amp-consent/amp-consent.md). | ||
|
|
||
| <<<<<<< HEAD |
There was a problem hiding this comment.
Here and below: merge conflicts
| */ | ||
| expandSyncIfAllowList_(href, allowList) { | ||
| return allowList | ||
| expandSyncIfAllowedList_(href, allowlist) { |
There was a problem hiding this comment.
nit: I think we are using allowlisted elsewhere.
|
|
||
| /** @const {!Object<string, boolean>} */ | ||
| const WHITELISTED_RPOPS = { | ||
| const ALLOWLISTED_RPOPS = { |
There was a problem hiding this comment.
ahhhhh RPOPSSSSSSSSSS --> PROPS
sorry for the driveby but this typo had me chuckling 😂
There was a problem hiding this comment.
That's amazing, absolutely didnt notice.
Enforce usage of allowlist instead of other terms.