feat: add optional validateAgainstSchema
option when creating user storage entry paths
#5326
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.
Explanation
This PR adds a new
validateAgainstSchema
option when creating user storage entry paths.This defaults to true, but can be relaxed to false when using the SDK.
SDK users should use the feature and key names they decide to use, and Controller users should follow the internal schema.
References
Related to: https://consensyssoftware.atlassian.net/browse/IDENTITY-31
Changelog
@metamask/profile-sync-controller
validateAgainstSchema
option when creating user storage entry pathsChecklist