User consent config validation - #84
Merged
EmilianoSanchez merged 7 commits intoMar 3, 2022
Merged
Conversation
EmilianoSanchez
changed the title
mmelograno
approved these changes
Mar 3, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Javascript commons library
What did you accomplish?
impressionsModeconfig param, to avoid a crash and default to 'OPTIMIZED' if a value is provided that is not a string.userConsentconfig param. Validation differs in server-side (NodeJS) and client-side (Browser), so the validation is done with a validator function that must be provided, same way thanruntimesettings validation.How do we test the changes introduced in this PR?
Extra Notes