-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add CHIP_ERROR object methods (#8784)
* Add CHIP_ERROR object methods #### Problem Having CHIP_ERROR be a class type provides type safety and the option to trace the source of errors. Since all platforms now use the class type, transitional code that provided for CHIP_ERROR to be either a class or integer type is no longer required and can be removed, which simplifies the class and some notation for using errors. #### Change overview - Remove the `CHIP_CONFIG_ERROR_CLASS` configuration option. - Add instance methods to replace the static `ChipError` functions, which were present to allow transitional integer overloads. To avoid breaking PRs in flight, the static methods remain present for now, marked “DO NOT USE”; they will be removed in a final cleanup PR. #### Testing Existing tests should confirm no change to functionality. * Rebase and regen to fix ZAP/Android after #8680 * Add assertions for bit fields
- Loading branch information
1 parent
203b25d
commit 0fe17ec
Showing
99 changed files
with
4,412 additions
and
4,586 deletions.
There are no files selected for viewing
66 changes: 22 additions & 44 deletions
66
examples/all-clusters-app/all-clusters-common/gen/IMClusterCommandHandler.cpp
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.