-
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
Fix 37422 #64215
Fix 37422 #64215
Conversation
Pinging @elastic/kibana-app-arch (Team:AppArch) |
Pinging @elastic/kibana-canvas (Team:Canvas) |
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.
Code LGTM so far! Glad you also took this opportunity to rename the Filter
interface to something more specific.
I think we will probably need a release_note:breaking
& dev docs writeup on this, unless the Canvas team feels otherwise.
@elasticmachine merge upstream |
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.
Looks good 👍
So the breaking issue will be if there are any 3rd party developers who are creating filters incorrectly, they will not function as expected?
Agree that there should be some Dev Documentation around this. Not sure where we document breaking changes to our plugin apis though?
@elasticmachine merge upstream |
Glad to see this fix! We definitely need to add a breaking-change release note, perhaps with a link to the issue, so anyone who has a plugin break understands why. |
@clintandrewhall ah, glad to see you back! |
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.
All good from my perspective 👍
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
* refactor: 💡 rename Filter -> ExpressionValueFilter * refactor: 💡 use new filter type in Canvas * fix: 🐛 fix tests after refactor Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
Summary
Closes #37422
Dev Docs
A breaking change was introduced to
filter
expression function. If you usedtype
argument offilter
function you now must usefilterType
instead.Old code:
New code:
The
type
field is used internally by expression interpreter to discriminate between different values it passes between functions.filter
function was the only function that exposed this field to users, after this change all expression values will consistently usetype
to determine a type of expression value.