fix: access token doesn't generate errors when token expires #45
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
There was a bug that caused an error when you tried to make, for the first time after a while, a new request. This request showed something like 'error getting user' and it was not a problem with the get_user function, it was a problem with the access token. The creation of a new token returns an array containing the 'success' message and the token generated by the API but, when the token is available, it returns only the token value because the process sends a request to the WP database. For that, a check for the access token response was added: when the response is an array it takes the value of the token from the array, when it isn't, it continues the process as always.
Testing instructions
You can test it by changing the expiration time of the access token and attempting to create a new request after the token has already expired.
Checklist for Merge