You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One more thing: this part does not look right to me.... Why are we generating things for client sides of clusters here?
Let's leave this as-is for now, but do a followup to not generate this... and probably not generate ClusterRevision for client clusters either, since it's not observable...
We need some metadata for client clusters, because Descriptor Cluster needs to be able to show info about them existing, right?
What we should not be generating are:
ClusterRevision attributes for client clusters, with space in the attr store and all that.
CommandList metadata bits for client clusters.
And I guess we could try to handle the Descriptor bits via some mechanism other than EmberAfCluster entries, but that will take a bit more surgery, whereas not generating the above two is an easy space win.
One more thing: this part does not look right to me.... Why are we generating things for client sides of clusters here?
Let's leave this as-is for now, but do a followup to not generate this... and probably not generate ClusterRevision for client clusters either, since it's not observable...
Originally posted by @bzbarsky-apple in #14299 (comment)
ZAP will generate meta for client cluster, but the client should not have cluster data per spec, should revisit related code in code base.
The text was updated successfully, but these errors were encountered: