-
Notifications
You must be signed in to change notification settings - Fork 61
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
Parse error of { on a separate line #56
Comments
landure
added a commit
to landure/shdoc
that referenced
this issue
Nov 9, 2022
landure
added a commit
to landure/shdoc
that referenced
this issue
Aug 17, 2023
…est#65) * Allow function bracket to be on next line, fix reconquest#56 * - Fix function name extraction for `function name {}`. (function declared with function keyword, but without parenthesis. - Add function declaraction unit tests.
landure
added a commit
to landure/shdoc
that referenced
this issue
Aug 17, 2023
…est#65) * Allow function bracket to be on next line, fix reconquest#56 * - Fix function name extraction for `function name {}`. (function declared with function keyword, but without parenthesis. - Add function declaraction unit tests.
landure
added a commit
to landure/shdoc
that referenced
this issue
Aug 17, 2023
landure
added a commit
to landure/shdoc
that referenced
this issue
Aug 17, 2023
…est#65) * Allow function bracket to be on next line, fix reconquest#56 * - Fix function name extraction for `function name {}`. (function declared with function keyword, but without parenthesis. - Add function declaraction unit tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This isn't parsed:
It is sufficient to put { in the same line of say-hello() to make it working but I don't like it.
Can it be fixed please?
The text was updated successfully, but these errors were encountered: