-
Notifications
You must be signed in to change notification settings - Fork 363
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
Trailing comma in an array end up in white-space #3997
Comments
Hi! We recently added validation indeed to flush out LST issues in our parsers. It's helpful to improve the parsers, but indeed might cause a test to fail until we circle back to the parser. I'd encountered this case as well and logged a test last week 78a55a4 We can keep your issue open to see that parser issue resolved; in the meantime you can remove that trailing comma from the test. Hope that helps! |
And perhaps good to note: This is only an internal modeling issue; your source code will still be reproduced faithfully even with that modeling mishap, as we have a separate check for that. So rest assured that any code changes will be just fine; it's only a matter of using compatible examples in tests until the parser correctly models the code. |
Another test case which can be enabled again once this is fixed: Lines 60 to 77 in 33d8f7d
|
rewrite bom 2.6.4, wasn't an issue on 2.5.3
Test failures when there is a trailing comma in an annotation. If I remove it, tests pass.
java.lang.AssertionError: Source file was parsed into an LST that contains non-whitespace characters in its whitespace. This is indicative of a bug in the parser.
So the comma at the end of
properties
in a test like thisThe text was updated successfully, but these errors were encountered: