-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Update script to sync operators automatically #200115
Conversation
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
# Conflicts: # packages/kbn-esql-validation-autocomplete/src/definitions/types.ts
description: i18n.translate('kbn-esql-validation-autocomplete.esql.definition.rlikeDoc', { | ||
defaultMessage: 'Filter data based on string regular expressions', | ||
}), | ||
}, | ||
{ name: 'not_rlike', description: '' }, | ||
].map(({ name, description }) => { |
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.
@stratoula Should we keep the internationalized descriptions for these functions? If we import the descriptions from Elasticsearch following this PR, I don't think they will be internationalized.
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 see we keep them in the other generated files such as https://github.com/elastic/kibana/blob/main/packages/kbn-esql-validation-autocomplete/src/definitions/generated/aggregation_functions.ts
Closing this PR in favor of #205565 that's more up-to-date |
Summary
Summarize your PR. If it involves visual changes include a screenshot or gif.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breaking
label should be applied in these situations.release_node:*
label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.