RedirectTo
in AuthorizeRequest
and Code
JSON field tag corrrected in TokenRequest
#7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
This PR
RedirectTo
field totypes.AuthorizeRequest
. This will be passed along in a request to the/auth/v1/authorize
endpoint.Code
intypes.TokenRequest
What is the current behavior?
Currently, there is no
RedirectTo
field intypes.AuthorizeRequest
: #4The field Code in
types.TokenRequest
has a wrong JSON name in the struct field tag: #5What is the new behavior?
/auth/v1/authorize
endpointCode
field's JSON name will be correct when/auth/v1/token
is called.