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
[ES|QL] Add support for command settings #175114
Conversation
/ci |
/ci |
Pinging @elastic/kibana-visualizations (Team:Visualizations) |
/ci |
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.
This is great, tested it locally and works fine. It would be awesome if we could give some love to our script with some comments/documentation. I am approving because except from that everything works great 👏
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.
Can you add a readme here about what this script does, how someone can run it etc? I am also happy if the readme is part of the file itself!
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.
ok, will add some more context there.
In theory the script should run automatically when the grammar is compiled, together with some existing file renaming script. So no "independent" run should make sense.
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 get that! Some context doesnt hurt though! No many details, just an explanation about what it does and why we are using it. It can be helpful for future reference.
/ci |
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.
SharedUX code changes LGTM.
💚 Build Succeeded
Metrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: |
## Summary Sync up with elastic/elasticsearch#103949 grammar changes. Command definitions now have a new `mode` list of argument, with related `ESQLCommandMode` at AST level. Validation now accepts settings and validate the specific ENRICH one (error message is taken from the ES codebase). Autocomplete doesn't trigger by default on settings, but it only trigger when user starts to type a setting with the `[` trigger char: ![enrich_modes](https://github.com/elastic/kibana/assets/924948/8882361d-2fc7-44ab-bc8e-3994fc3e733d) Note that multiple settings are supported, but shadowing will trigger a warning. `ccq.mode` value name and descriptions have been taken from the linked ES PR. ### Checklist - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
## Summary Sync up with elastic/elasticsearch#103949 grammar changes. Command definitions now have a new `mode` list of argument, with related `ESQLCommandMode` at AST level. Validation now accepts settings and validate the specific ENRICH one (error message is taken from the ES codebase). Autocomplete doesn't trigger by default on settings, but it only trigger when user starts to type a setting with the `[` trigger char: ![enrich_modes](https://github.com/elastic/kibana/assets/924948/8882361d-2fc7-44ab-bc8e-3994fc3e733d) Note that multiple settings are supported, but shadowing will trigger a warning. `ccq.mode` value name and descriptions have been taken from the linked ES PR. ### Checklist - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
## Summary Sync up with elastic/elasticsearch#103949 grammar changes. Command definitions now have a new `mode` list of argument, with related `ESQLCommandMode` at AST level. Validation now accepts settings and validate the specific ENRICH one (error message is taken from the ES codebase). Autocomplete doesn't trigger by default on settings, but it only trigger when user starts to type a setting with the `[` trigger char: ![enrich_modes](https://github.com/elastic/kibana/assets/924948/8882361d-2fc7-44ab-bc8e-3994fc3e733d) Note that multiple settings are supported, but shadowing will trigger a warning. `ccq.mode` value name and descriptions have been taken from the linked ES PR. ### Checklist - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
Summary
Sync up with elastic/elasticsearch#103949 grammar changes.
Command definitions now have a new
mode
list of argument, with relatedESQLCommandMode
at AST level.Validation now accepts settings and validate the specific ENRICH one (error message is taken from the ES codebase).
Autocomplete doesn't trigger by default on settings, but it only trigger when user starts to type a setting with the
[
trigger char:Note that multiple settings are supported, but shadowing will trigger a warning.
ccq.mode
value name and descriptions have been taken from the linked ES PR.Checklist