JSON responses for the Login controller/snippet #121
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ehooks,posthooks and login. Todo: success response.
…ogin. Needs a lot of testing.
|
Available with 1.9.7 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added JSON responses for the Login snippet/controller.
Needs a fair amount of testing as it's more complex than than the register controller done previously and I'm not 100% sure I've covered all situations.
For there to be success messages passed in the json response, in the snippet the parameters
loginMsgandlogoutMsgshould be filled out. Error messages are generated in the same manner as a non-json response.