Closed caspg closed 5 years ago
oauth2
doesn't include Poison
because the serializers are configurable. It only configures Poison
by default as a convenience. You still need to include it in your app.
I do have this PR that I've posted for over a year and I haven't merged it yet: https://github.com/scrogson/oauth2/pull/92
I guess I'm still waiting for feedback from the community on whether it's a good approach or not.
I've solved this problem just including {:poison, "~> 3.1"} on my dependencies.
Is there a reason we're required to use Poison
when the we can customize the serializer for Ueberauth
(with the default being Jason
)?
I'm getting following error when using with
oauth2 v0.9.2
.ouath2
removedPoison
from dependencies (changelog) but it is still configured as a default serializer.Adding
Poison
to dependencies (ueberauth_github or to my phoenix app) solves this problem. Another way is to configureoauth2
(click) serializer and use for exampleJason
which comes by default withPhoenix
.Is there any info about it that I missed? If not, it could be useful to add it to the README.