-
Notifications
You must be signed in to change notification settings - Fork 48
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
Expose utils for expression LSP #117
Conversation
c1a9a33
to
801fbaf
Compare
/canary |
/canary |
Codecov ReportBase: 79.07% // Head: 79.10% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #117 +/- ##
==========================================
+ Coverage 79.07% 79.10% +0.03%
==========================================
Files 132 132
Lines 4655 4662 +7
Branches 1164 1167 +3
==========================================
+ Hits 3681 3688 +7
Misses 688 688
Partials 286 286
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
|
||
// Expressions can be separated by semicolons, commas, or just inferred without any | ||
// separators | ||
if (chIndex === SEMCOL_CODE || chIndex === COMMA_CODE) { |
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.
Would there be any worth to having the kind of characters that are ignored be configurable?
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.
That may make it pretty difficult to define a proper bnf grammar for expressions. But that might be worth considering as a future change
Release Notes
parseExpression
from the expression parserstrict
flag toparseExpression
that will (when disabled) attach any parsing errors to the top-level node instead of throwing