feat: make configuration page as optional #1521
Draft
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
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.
Issue number:
ADDON-76819
PR Type
What kind of change does this PR introduce?
Summary
Set configuration as an optional key in
globalConfig.json.Changes
Made configuration page optional in
schema.json, So that users can have an add-on UI without Configuration page.Also added a smoke testcase which captures this behaviour.
User experience
Now, user can build their add-on without specifying
configurationin theirglobalConfig.json. Users now can have a UI without Configuration page for their add-on.Checklist
If an item doesn't apply to your changes, leave it unchecked.