-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[ES|QL] [Controls] Fixes fields values not available after editing #268102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
stratoula
wants to merge
5
commits into
elastic:main
from
stratoula:esql-control-fix-fields-dropdown
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
9df1dcc
[ES|QL] [Controls] Fixes fields available values not available after …
stratoula 3f6e7b7
Add a test to safeguard for another regression
stratoula b8d3694
Merge branch 'main' into esql-control-fix-fields-dropdown
stratoula 89868f7
Merge branch 'main' into esql-control-fix-fields-dropdown
stratoula 531b1b7
Merge branch 'main' into esql-control-fix-fields-dropdown
stratoula File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this is the right approach. By adding it to the user-facing API schema like this, it is up to the user who makes the control to copy paste the query from some other ES|QL query into this and then we somehow have to keep these values up-to-date... Not good!
Instead, I wonder if we could use the related panels logic once that merges in order to determine which query to use at runtime? Especially with my suggested approach - if we move the related panels logic into the ES|QL control like I suggested, we could pretty easily know which ES|QL query is using the field control variable at runtime, which we could then use to populate the suggested options dropdown. What do you think @stratoula?
cc @Zacqary here, too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah I see what you say and I hear it. I am fine with fixing it the way you suggest Hannah. I am going to close this PR but can you please handle it? It is a bad regression and I dont like it 🙏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created an issue to track: #268695