Add type validation to the default_preferences
generation (PR 10548 follow-up)
#10610
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.
The generated
default_preferences.json
file is necessary when initializing the Firefox preferences, which only supports certain types, hence this patch adds additional validation to help prevent run-time errors in Firefox.Given that these changes add a code-path to
AppOptions.getAll
which could throw, theOptionKind.PREFERENCE
branch is also modified to require exact matching to prevent (future) errors in the viewer.Finally the conditionally defined
defaultOptions
will no longer (potentially) be considered during thegulp default_preferences
task, to make it more difficult for them to be accidentally included.