Skip to content
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

Merged
merged 2 commits into from
Jul 13, 2023

Conversation

Skaiir
Copy link
Contributor

@Skaiir Skaiir commented Jul 12, 2023

Copy link
Contributor

@pinussilvestrus pinussilvestrus left a 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 !

@Skaiir
Copy link
Contributor Author

Skaiir commented Jul 12, 2023

@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);
Copy link
Contributor

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.

@pinussilvestrus pinussilvestrus merged commit b17c223 into develop Jul 13, 2023
10 checks passed
@pinussilvestrus pinussilvestrus deleted the test-case-team-hto-279 branch July 13, 2023 07:28
@bpmn-io-tasks bpmn-io-tasks bot removed the needs review Review pending label Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants