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

Qute parser does not parse operator parameters with '=' correctly #742

Closed
JessicaJHee opened this issue Sep 13, 2022 · 0 comments · Fixed by #745
Closed

Qute parser does not parse operator parameters with '=' correctly #742

JessicaJHee opened this issue Sep 13, 2022 · 0 comments · Fixed by #745
Labels
bug Something isn't working qute
Milestone

Comments

@JessicaJHee
Copy link
Contributor

Operators used in #case or #is sections that include the = character does not get parsed correctly.

Ex:
{#case <= 10}

In this case, for operators <= or >=, the parser only scans < or > as the parameter since = is assumed to be the end of a token in the parser and is cut off from the parameter.

angelozerr pushed a commit to angelozerr/quarkus-ls that referenced this issue Sep 14, 2022
angelozerr pushed a commit to angelozerr/quarkus-ls that referenced this issue Sep 14, 2022
angelozerr pushed a commit to angelozerr/quarkus-ls that referenced this issue Sep 14, 2022
@datho7561 datho7561 added this to the 0.13.0 milestone Sep 14, 2022
@datho7561 datho7561 added bug Something isn't working qute labels Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working qute
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants