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

Migrate from Poison to Jason (Phoenix 1.4) #2046

Open
ysbaddaden opened this issue Feb 7, 2022 · 1 comment · May be fixed by #2237
Open

Migrate from Poison to Jason (Phoenix 1.4) #2046

ysbaddaden opened this issue Feb 7, 2022 · 1 comment · May be fixed by #2237
Assignees
@leandroradusky
Labels
tech-debt :octocat:

Comments

@ysbaddaden
Copy link
Contributor

Phoenix 1.4+ can use either Poison or Jason for its own parse/dump JSON (be it internal or implicit). Phoenix now recommends Jason, and it's supposed to be faster, but there seemed be some issues, so I'm sticking to Poison for now.

We also use Poison explicitly to parse/dump JSON in Surveda. We could probably migrate those cases to use Jason.

Refs #2019
@diegoliberman
Copy link
Contributor

Removed pending estimation: 8h

@leandroradusky leandroradusky self-assigned this Apr 6, 2023
@leandroradusky leandroradusky linked a pull request Apr 6, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@leandroradusky leandroradusky

Labels
tech-debt :octocat:
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Migrate Poison to Jason instedd/surveda
3 participants
@ysbaddaden @leandroradusky @diegoliberman