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.

Sign up for GitHub

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

Jump to bottom

Consider using ktn_dodger instead of epp_dodger for parsing #25

Closed
juanbono opened this issue Nov 16, 2019 · 1 comment
Closed

Consider using ktn_dodger instead of epp_dodger for parsing #25

juanbono opened this issue Nov 16, 2019 · 1 comment
Assignees
@juanbono
Labels
research

Comments

@juanbono
Copy link
Collaborator

juanbono commented Nov 16, 2019 •
edited by elbrujohalcon
Loading

We can try using ktn_dodger from katana-code, after inaka/katana-code#31 is merged, instead of epp_dodger to parse the source files.
@elbrujohalcon elbrujohalcon changed the title Consider using Aleppo instead of epp_dodger for parsing Consider using ktn_dodger instead of epp_dodger for parsing Nov 29, 2019
@juanbono juanbono self-assigned this Dec 2, 2019
juanbono added a commit that referenced this issue Dec 11, 2019
@juanbono
[#25] Replace epp_dodger with ktn_dodger (#35)
59fec27 
* add katana-code

* replace epp_dodger with ktn_dodger

* add file for testing number formatting

* uncomment post_hooks

* use katana-code from hex.pm

* update rebar.lock

* add katana_code to applications

* update katana-code version

* add katana_code bin to format script
@juanbono
Copy link
Collaborator Author

Now we use katana-code instead of epp_dodger (#35 ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@juanbono juanbono

Labels
research
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@juanbono