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

number() should return null instead of failing the evaluation #731

Open
saig0 opened this issue Sep 25, 2023 · 0 comments · May be fixed by #853
Open

number() should return null instead of failing the evaluation #731

saig0 opened this issue Sep 25, 2023 · 0 comments · May be fixed by #853

Comments

@saig0
Copy link
Member

saig0 commented Sep 25, 2023

Describe the bug
I use the function number() to convert a string into a number. If the string is not a number then the evaluation fails.

An evaluation failure is unexpected and it doesn't allow to handle this case.

To Reproduce
Steps to reproduce the behavior:

  1. Evaluate the expression
number("x")
  1. Verify that the evaluation fails

Expected behavior
The function should return null if the string is not a valid number.

See the TCK test case 0058-feel-number-function.

Environment

  • FEEL engine version: 1.17.0
  • Affects:
    • Camunda Automation Platform 7: [7.x]
    • Zeebe broker: [0.x]

Related to #623

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant