-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore matter unit tests and fix backwards compatibility. #948
Restore matter unit tests and fix backwards compatibility. #948
Conversation
Codecov Report
@@ Coverage Diff @@
## master #948 +/- ##
==========================================
- Coverage 62.13% 62.01% -0.12%
==========================================
Files 155 155
Lines 16624 16661 +37
Branches 3674 3687 +13
==========================================
+ Hits 10330 10333 +3
- Misses 5596 5627 +31
- Partials 698 701 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
This work also uncovered the fact that |
…erated struct. Previous change just added them directly in the generation code, which promptly destroyed all backwards compatibility. With this approach, the default zap generates as it "always did", but you can request an override to do things like add new elements, or reorder them. This should go hand it hand with the PR: project-chip/zap#948 If ZAP PR gets merged first, Matter will stay broken with latest zap until this commit is merge in. Matter, however, can merge this commit first without ill effect, and use older zap if it chooses.
…erated struct. (#25316) Previous change just added them directly in the generation code, which promptly destroyed all backwards compatibility. With this approach, the default zap generates as it "always did", but you can request an override to do things like add new elements, or reorder them. This should go hand it hand with the PR: project-chip/zap#948 If ZAP PR gets merged first, Matter will stay broken with latest zap until this commit is merge in. Matter, however, can merge this commit first without ill effect, and use older zap if it chooses.
…erated struct. (#25316) Previous change just added them directly in the generation code, which promptly destroyed all backwards compatibility. With this approach, the default zap generates as it "always did", but you can request an override to do things like add new elements, or reorder them. This should go hand it hand with the PR: project-chip/zap#948 If ZAP PR gets merged first, Matter will stay broken with latest zap until this commit is merge in. Matter, however, can merge this commit first without ill effect, and use older zap if it chooses.
…erated struct. (project-chip#25316) Previous change just added them directly in the generation code, which promptly destroyed all backwards compatibility. With this approach, the default zap generates as it "always did", but you can request an override to do things like add new elements, or reorder them. This should go hand it hand with the PR: project-chip/zap#948 If ZAP PR gets merged first, Matter will stay broken with latest zap until this commit is merge in. Matter, however, can merge this commit first without ill effect, and use older zap if it chooses.
No description provided.