Prevent a fatal error when API request fails #163
Merged
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.
Description of the Change
We had an issue where API credentials were revoked and it caused a fatal error on our site. This error originated in the code that gets a list of all available players. The request to get the players will fail and we have a
is_wp_error
check on that but we don't check for that until after we try and use the returned value (which causes fatals if that value is an error).This PR moves that check up prior to us trying to use that value and also adds a check to ensure the returned value isn't
false
.Alternate Designs
None
Benefits
Prevent fatal errors if API credentials are revoked.
Possible Drawbacks
None
Verification Process
This fix was pushed into our staging environment that was experiencing the fatal errors and this resolved those
Checklist: