Throw an exception if the access token request failed #219
Conversation
This file contains hidden or 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
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.
Rather than returning null if the access token request fails, the
getAccessToken()method inAuthHelper.phpshould throw anSdkExceptionso that when the method is invoked in a try-catch the developer can choose how to act upon a bad request (usually HTTP 400).This can happen when trying to request an access token twice with the same authorisation code, which can happen if the user installing the Shopify app refreshes the callback route. The user might do this by accident, by using page navigation in their browser or when the developers app crashes on that route. If this does happen, then the developer may choose to redirect them back to Shopify safely, rather than trying to move ahead with using a null access token.