Fix custom type docs on "Intermediate usage" and docstring #434
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.
Both the
intermediate usage
example on custom types and the related docstrings in theArgument
class are quite confussing for newcomers:True
draws a clearer picture of the expected behaviour one custom type.email
example function and theArgument
docstring reference aValidationError
exception which is not present on source and is actually not required (any raised exception will do for converting/validating types).