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

error_payload/1 does not match Ecto.Changeset case as suggested in Docs #7

Open
Waasi opened this issue Mar 17, 2018 · 1 comment
Open

Comments

@Waasi
Copy link

Waasi commented Mar 17, 2018

Hello,

I am having trouble using the error_payload/1 function in my resolvers. The error is a match error when I pass an Ecto.Changeset as argument. I am willing to work on this and submit a PR, but, I wanted to open a discussion about the approach. Should I update the docs or should I implement the case function for Ecto.Changeset?

The line that says that error_payload can take an Ecto.Changeset: here

The implementation: here

@sean-clayton
Copy link

Just ran into this issue as well. Doesn't seem to work at all with changesets which is why I wanted to use kronky in the first place 👀

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

No branches or pull requests

2 participants