-
Notifications
You must be signed in to change notification settings - Fork 104
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(FEEL): vars in filters are properly parsed #711
Conversation
8461dc4
to
dc596fd
Compare
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.
Really nice 👍
👍 for all the additional test cases !
packages/form-js-viewer/test/spec/util/GetSchemaVariables.spec.js
Outdated
Show resolved
Hide resolved
dc596fd
to
8c9a139
Compare
@pinussilvestrus Fixed the one comment and also decided to filter null and undefined variables. Mostly so that we don't ever get that issue again. |
variables = [ ...variables, ...templateVariables ]; | ||
} | ||
}); | ||
|
||
return variables; | ||
return variables.filter(variable => variable !== undefined || variable !== null); |
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.
Not 100% sure about this one. The good thing about the current behavior (keeping null values) was that we catched the error in Tasklist really easily and it didn't slip our attention. However we should not crash the whole workflow, so I believe it's fine now.
Related to https://github.com/camunda/team-hto/issues/279