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

Make the JSON decoder configurable #24

Closed
lee-dohm opened this issue May 30, 2019 · 1 comment · Fixed by #30
Closed

Make the JSON decoder configurable #24

lee-dohm opened this issue May 30, 2019 · 1 comment · Fixed by #30

Comments

@lee-dohm
Copy link
Owner

Basically, I don't want to have to deal with JSON dependency conflicts anymore.
@lee-dohm
Copy link
Owner Author

lee-dohm commented Jun 4, 2019

Or pre-convert the two JSON files to their equivalent .exs files and then no JSON decoder is necessary in the production environment?

This was referenced Jun 4, 2019
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove the runtime dependency on Jason lee-dohm/octicons-ex
1 participant
@lee-dohm