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

Updates #237

Merged
merged 5 commits into from
May 4, 2024
Merged

Updates #237

merged 5 commits into from
May 4, 2024

Conversation

amaanq
Copy link
Member

@amaanq amaanq commented May 4, 2024

Closes #234

@amaanq
Copy link
Member Author

amaanq commented May 4, 2024

/cc @calebdw you're probably interested 😁

@amaanq amaanq merged commit d5e1bfe into tree-sitter:master May 4, 2024
6 checks passed
@calebdw
Copy link
Collaborator

calebdw commented May 5, 2024

@amaanq, thanks!

I guess I was missing the token.immediate in the string_content rule...

I have a few questions though:

  • it looks like you removed the parse examples script...is there any way to run this outside of ci?
  • there seems to be a lot of string_contents in the added testcase:
                (string
                  (string_content)
                  (string_content)
                  (string_content)
                  (string_content)
                  (string_content)
                  (string_content)
                  (string_content)
                  (escape_sequence)
                  (string_content)
                  (string_content))
    but should they not be condensed into a single node on either side of the escape sequence?
                (string
                  (string_content)
                  (escape_sequence)
                  (string_content))
  • it looks like all of the build scripts in the package.json were replaced by the prebuildify? If so that's pretty neat

@amaanq
Copy link
Member Author

amaanq commented May 5, 2024

huh good point, I'll look at the string stuff in a bit

as to running examples outside of ci, no not really, since it was just cluttering the repo imo - if CI fails there's an option to make it upload the failed files (check example in parse-action repo), and so you can just download it from there - otherwise for local dev you can just copy the git clone commands in the ci file, and run ts p examples/**/*.php -q

yeah prebuildify is very nice, esp now that we've moved to napi from nan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Parsing error
2 participants