fix: move extension properties to preferences #948
Merged
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.
What does this PR do?
Make preferences visible (and only the one with the default scope) when adding simple properties to an extension.
Screenshot/screencast of this PR
What issues does this PR fix or reference?
#947
How to test this PR?
Add some properties (like in podman package.json file)
and look if you see them appear in the preferences screen.
Change-Id: If8889eae5c1ef13232d22fe2539b941b728e2fef
Signed-off-by: Florent Benoit fbenoit@redhat.com