-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Restyle [im] Fix wildcard path support per spec #11175
Conversation
The cluster info should be breaked into AttributeInfo and EventInfo.connectedhomeip/src/app/ClusterInfo.h Lines 34 to 44 in 845b78c
This comment was generated by todo based on a
|
(#8364): Support wildcard paths here, should check if we have got valid input when implementing wildcard read.connectedhomeip/src/app/ReadHandler.cpp Lines 336 to 346 in 845b78c
This comment was generated by todo based on a
|
(#8364): We assume the path is a concrete path here, will be removed when implementing the wildcard read.connectedhomeip/src/app/ReadHandler.cpp Lines 346 to 352 in 845b78c
This comment was generated by todo based on a
|
We assume the path is a concrete path here, will be removed when implementing the wildcard event read.connectedhomeip/src/app/ReadHandler.cpp Lines 384 to 390 in 845b78c
This comment was generated by todo based on a
|
We assume the path is a concrete path here, will be changed when implementing the wildcard event read.connectedhomeip/src/app/reporting/Engine.cpp Lines 69 to 79 in 845b78c
This comment was generated by todo based on a
|
A duplicate of #11115 with additional commits that automatically address
incorrect style, created by Restyled.
Please review accordingly.
Since the original Pull Request was opened as a fork in a contributor's
repository, we are unable to create a Pull Request branching from it with only
the style fixes.
The following Restylers made fixes:
To incorporate these changes, you can either:
Merge this Pull Request instead of the original, or
Ask your contributor to locally incorporate these commits and push them to
the original Pull Request
Expand for example instructions
NOTE: As work continues on the original Pull Request, this process will
re-run and update (force-push) this Pull Request with updated style fixes as
necessary. If the style is fixed manually at any point (i.e. this process finds
no fixes to make), this Pull Request will be closed automatically.
Sorry if this was unexpected. To disable it, see our documentation.