✨ [amp-consent] Sync and store purposeConsents
in localStorage
#32721
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Partial for #31607
Alter what it means to have a stored value; we now must have consent decisions for every purpose consent listed in the
purposeConsentRequired
field (either inline or from remote response).In the case of an already stored consent decision, sync new consent discussions (
purposeConsents
) viacheckConsentHref
, which will be reflected on next page visit.Store the
purposeConsents
in local storage under the same namespace as the existing consent information under the keypc
:Also did some cleaning up of tests (function* to preferred async/await pattern).