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

[Backport 1.16] fix: Parse expression with NBSP character #915

Merged
merged 5 commits into from
Aug 29, 2024

Conversation

backport-action
Copy link
Collaborator

Description

Backport of #914 to 1.16.

relates to #840
original author: @saig0

Add new test cases to verify that a NBSP and other space characters can be parsed.

(cherry picked from commit f8f3f78)
Adjust the whitespace handling of the parser to ignore FEEL-specific whitespaces as defined in the DMN specification.

The JavaWhitespace class worked very well because it supported also Java-like comments, as required by the DMN specification. Instead of adding additional whitespace rules for the individual parsers, extend the JavaWhitespace class by making a copy of it. This is less error-prone, easier to maintain, and more efficient.

(cherry picked from commit 8b691b9)
Some whitespace characters were treated as part of the list iteration variable name. As a result, the parsing failed because the keyword "in" was not found.

Fix the parsing issue by excluding whitespace characters as part of the variable name.

(cherry picked from commit 08ef5a4)
@saig0 saig0 merged commit 7cab1f5 into 1.16 Aug 29, 2024
3 checks passed
@saig0 saig0 deleted the backport-914-to-1.16 branch August 29, 2024 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants