Clarify that error.type should be the fully-qualified exception class name (if applicable) when it represents an exception type
#387
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
trask
force-pushed
the
error-type-fully-qualified
branch
from
360079d
to
53a18ba
Compare
lmolkova
approved these changes
Oct 12, 2023
Oberon00
reviewed
Oct 12, 2023
mateuszrzeszutek
approved these changes
Oct 12, 2023
Oberon00
approved these changes
Oct 13, 2023
joaopgrassi
approved these changes
Oct 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #386
Changes
Clarifies that
error.typeshould be the fully-qualified exception class name (if applicable) when it represents an exception type.Merge requirement checklist
schema-next.yaml updated with changes to existing conventions.