-
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
Improve version
type support
#123739
Improve version
type support
#123739
Conversation
version
type support
@@ -345,7 +345,7 @@ class FilterEditorUI extends Component<Props, State> { | |||
|
|||
private renderParamsEditor() { | |||
const indexPattern = this.state.selectedIndexPattern; | |||
if (!indexPattern || !this.state.selectedOperator) { | |||
if (!indexPattern || !this.state.selectedOperator || !this.state.selectedField) { |
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.
logically it couldn't happen that we had selectedOperator
without a selectedField
, but I wanted to clarify this here because children now have field
as required
}); | ||
} | ||
|
||
export function validateParams(params: any, type: string) { | ||
switch (type) { | ||
export function validateParams(params: any, field: IFieldType) { |
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.
because we need to check against field.esTypes
now, I am passing the whole field object
Pinging @elastic/kibana-app-services (Team:AppServicesSv) |
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.
LGTM
@elasticmachine merge upstream |
ACK, will review |
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.
LGTM, tested a-la-carte, works as expected
Discover isn't consistent in usage. TODO: create issue for discover
Agreed, didn't have time to look into it, so creating an issue is appreciated 👍
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
Summary
close #93248
This pr improves support for semantic version field type in Kibana
version
fields to the filter managerversion
specific icon to<FieldIcon/>
component (see discussion [EuiIcon] AddtokenVersion
eui#5520)Known issues:
version
field in elasticsearch. I turned it off until it is supported - TODO: link es issue<FieldIcon/>
usage. [Discover]<FieldIcon/>
usage is inconsistent #124017version
#124015How to test
See added functional test
Release notes
Version field type improvements