-
Notifications
You must be signed in to change notification settings - Fork 89
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
add request token event #49
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @jr-k!
Thanks for your PR 🙂
Could you add some unit tests as well?
Moreover, there are some unneeded blank lines that must be removed in order to follow the current coding standards
Some what ? Never heard of "tests". Joke aside, I'm not very good nor familiar at writing tests (Shame on me). Here is a commit for blank lines. |
@jr-k Time to level up then? :) Jokes aside, thanks for the PR. Also, some code quality checks of our CI are broken with this change. |
Here we are, no conflicts and tests, alright ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect 👌
Is there a merge date policy ? I need this in production, I can use my fork but I would like to avoid that. |
d5f8c6b
to
7be39ea
Compare
Thank you @jr-k. |
This PR was squashed before being merged into the 0.1-dev branch. Discussion ---------- Fix request token event I think #49 was merged too soon. This PR tries to fix the following flaws: 1. The test expectation is wrong. 2. The event listener in the test is being added after the event dispatch. 3. The response set to the event is being discarded by the controller. Commits ------- f14c02d Fix request token event
I've added an event to manipulate the response during /token process. Useful to add some Set-Cookie directives for example.