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

Don't use lua-format for output normalisation #31

Open
jparoz opened this issue Feb 25, 2023 · 0 comments
Open

Don't use lua-format for output normalisation #31

jparoz opened this issue Feb 25, 2023 · 0 comments
Labels
improvement Improves the way that an existing feature works, in a backwards-compatible way.
Milestone

Comments

@jparoz
Copy link
Owner

jparoz commented Feb 25, 2023

We can probably just use an off-the-shelf Lua parser to parse, and implement some simple renderer of the parsed tree.

This would also be useful in parsing of our actual files, because then we can validate that the contents of lua {...} blocks is at least valid Lua syntax, or validate that it is a valid Lua expression, or even validate that it's a valid Lua expression which only depends on things it's allowed to from the Huck scope! As well as validating foreign export paths.

@jparoz jparoz added this to the 0.8.0 milestone Feb 25, 2023
@jparoz jparoz added the improvement Improves the way that an existing feature works, in a backwards-compatible way. label Feb 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improves the way that an existing feature works, in a backwards-compatible way.
Projects
Status: Todo
Development

No branches or pull requests

1 participant