Move selectors to a column #85
Merged
Conversation
This file contains hidden or 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
andresmgot
requested review from
a team,
sarahzinger and
vickyyyyyyy
and removed request for
a team
sarahzinger
approved these changes
Oct 13, 2021
| value={column || null} | ||
| fetch={fetchColumns} | ||
| onChange={(e) => onColumnChange(e?.value)} | ||
| // TODO: Add schema as dependency |
Contributor
There was a problem hiding this comment.
do you want to keep this todo?
Contributor
Author
There was a problem hiding this comment.
yes, it needs this grafana/sqlds#47 first
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Follow up of #84
To follow the same approach than Athena (and other SQL datasources in the future), I moved the schema/table/column selectors to a column: