Config editor: Migrate to new form styling under feature toggle #244
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
idastambuk
changed the title
kevinwcyu
approved these changes
Nov 18, 2023
idastambuk
force-pushed
the
config-editor-migration
branch
from
2fa50c3
to
062d662
Compare
Closed
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.
What this PR does / why we need it:
Migrating Config Editor to the new design system form components
The new components are under a Grafana feature flag
awsDatasourcesNewFormStyling.Config Editor
What was done
Replace the editor inline fields for the grafana/ui Field components if the feature flag is enabled
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: