Repository navigation
refactor!: rename exceptions module to error - #8
Merged
Merged
Conversation
This file contains hidden or 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
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.
Move the library's error definitions from
cdpify.exceptionstocdpify.errorso the module matches the publicCDPErrornaming.All internal and test imports now use the new module. Root-package error exports, the class hierarchy, and existing deprecated class aliases retain their behavior.
Breaking change:
cdpify.exceptionsis removed. Replace imports such as:with:
from cdpify import CDPCommandErrorcontinues to work. README and the Unreleased changelog document the migration.Validation: