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

refactor: move parser to a separate crate #467

Merged
merged 5 commits into from
Jun 26, 2023
Merged

Conversation

rszyma
Copy link
Contributor

@rszyma rszyma commented Jun 25, 2023

Will close #463

@rszyma rszyma changed the title WIP: Refactor parser WIP: Move parser to a separate crate Jun 25, 2023
@rszyma rszyma changed the title WIP: Move parser to a separate crate refactor: move parser to a separate crate Jun 25, 2023
@rszyma rszyma marked this pull request as ready for review June 25, 2023 18:45
@jtroo
Copy link
Owner

jtroo commented Jun 26, 2023

The parser tests are failing due file path changes, though it's not being caught in github actions because github actions currently does not test the crate. I can fix the github actions later, but it would be good to make the tests pass in this PR.

@jtroo
Copy link
Owner

jtroo commented Jun 26, 2023

Also, would be good to add a .gitignore for the Cargo.lock that can get generated in parser.

@jtroo jtroo merged commit 1f63e76 into jtroo:main Jun 26, 2023
3 checks passed
@rszyma rszyma deleted the refactor-parser branch June 26, 2023 19:12
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.

Refactor proposal: move parser to a separate crate
2 participants