DIA-3187 handle state consent strings #528
Merged
Conversation
This file contains 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
andresilveirah
changed the base branch from
develop
to
DIA-2030_add_support_to_usnat
15 tasks
| Set to true if in the response of `/meta-data`, the applicableSections returned is different than the one stored. | ||
| Used as part of the decision to call `/consent-status` | ||
| */ | ||
| var needsNewUSNatData = false |
carmelo-iriti
approved these changes
Dec 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR has a little bit of extra code / refactoring than necessary for the feature:
MetaDataResponse.GDPR._idtovendorListId(unrelated to the feature)error.failureReason(this is always nil) toerror.description(unrelated to the feature)applicableSectionstoMetaData.USNatresponse and call/consent-statusif it changes.