-
Notifications
You must be signed in to change notification settings - Fork 381
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
Calling encode_from_hooked causes error after recent commit #247
Comments
+1 Seeing this as well. |
doomspork
pushed a commit
that referenced
this issue
Jan 5, 2017
Could you also retire this version or release a new version? Right now, if you don't fix the version to 0.14.0, you'll hit the issue. |
0.14.2 has been released. I'll retire 0.14.1 later today. |
Hanspagh
pushed a commit
to Hanspagh/guardian
that referenced
this issue
Nov 1, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Commit 1deca7f changed the pattern matching in guardian.ex line 100 from
:ok
to{:ok, _}
:But the default return value of the
after_encode_and_sign
is still just:ok
, so we get the errorno case clause matching: :ok
.hooks.ex:
def after_encode_and_sign(_, _, _, _), do: :ok
The text was updated successfully, but these errors were encountered: