Handle access_denied from Hello, update README #1
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.
When a user decides to not proceed with hellō, the user is redirected back to the configured
callback
URL with the following:This PR checks if the hash contains and error, redirects to the backend and returns a
403
if it is denied.An alternative behavior would be to redirect back to
/
and have a message bubble saying Hello OAuth flow cancelled.Docs:
Testing:
Code can be played around here: http://next-with-hello-leewc.vercel.app/ (or copy paste the URL above to simulate the behavior).
I cloned the repo using Vercel (which unfortunately makes the repo a standalone/not a Github fork, so I had to test and then cherry-pick the commit over).