Updated notes on using a cache
instance when initializing OAuth
.
#693
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.
What kind of change does this PR introduce? (check at least one)
The Flask OAuth Client documentation excludes important information about creating a
cache
instance forOAuth
initialization.Under FlaskClient
framework_integration.py
source code,You are required to have a
delete
method for thecache
object else you get anAttributeError
like thisAttributeError("'Cache' object has no attribute 'delete'")
.This PR updates the documentation to inform users about the need to have a
delete
method as part of theircache
instance.