This pull request update's Gateway's included OAuth exceptions to be more clear – they have more helpful error messages, powered by Laravel 5.5 renderable exceptions & the correct 401 status code, ensuring spec-compliant OAuth clients work out of the box!
How should this be reviewed?
I've tested this alongside my local Rogue, and updated the corresponding unit tests.
Note: for apps that are not on Laravel 5.5 (just Phoenix Next, I believe) we can always catch these exceptions in the handler and call the exception's render method manually.
What's this PR do?
This pull request update's Gateway's included OAuth exceptions to be more clear – they have more helpful error messages, powered by Laravel 5.5 renderable exceptions & the correct
401
status code, ensuring spec-compliant OAuth clients work out of the box!How should this be reviewed?
I've tested this alongside my local Rogue, and updated the corresponding unit tests.
Checklist