Fix misplaced parenthesis in custom scalar docs #3401
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.
The implementation of the Base64 custom scalar given in the docs differs from the implementation actually used. The implementation currently shown in the docs raises an AttributeError when used. It appears that the docs were originally created with an extra stray close paren, and the wrong one was deleted when that was fixed.
Description
It's the user's input that needs to be encoded as
bytes
, not the output ofbase64.b64decode
, which is alreadybytes
.Types of Changes
Checklist