Display warnings for provisional Matter clusters

[ethanzhouyc]

JIRA: ZAPP-1571

• Display a warning icon and message for enabled provisional clusters in Matter, ensuring compatibility with existing cluster warnings.
• Add warnings for enabled provisional clusters to the notification system using SQL triggers.

[brdandu]

We get a warning when a provisional cluster is enabled? Could you give an example?

[ethanzhouyc]

Yes, warnings appear only when a provisional cluster is enabled. Showing warnings for all provisional clusters by default would create unnecessary distractions for users.

For example, the Chime Cluster is marked as provisional in its XML (<cluster apiMaturity="provisional">). Warning icon with messages and notifications will be displayed if user enables the cluster

[brdandu]

Since this is needed not as a test but for calculation. Do you think this should go into beforeAll ?

[ethanzhouyc]

I think beforeAll() should be limited to db setup and package loading. While cluster insertion is for calculation, future ZAP changes might affect it. Placing it in a separate module with expect() assertions ensures failures are easily traceable.

[brdandu]

I was wondering if we ever run into an issue where the below test runs before this in an asynchronous way and clusterId is not populated. I remember we had this issue at one point. Forgot how we resolved that. You will not face that issue if you put this in beforeAll however.

[ethanzhouyc]

@brdandu Improvements in new commits:

1. provisional cluster warnings are set in the notification pane and printed to the console on opening a ZAP file
2. add unit tests for setting provisional cluster warnings on opening a ZAP file

I added <cluster apiMaturity="provisional"> to scene.xml for testing purpose. (The cluster is marked as provisional in CHIP repo). The added unit tests require adding a new .zap file with enabled provisional cluster.

[brdandu]

I was wondering if we ever run into an issue where the below test runs before this in an asynchronous way and clusterId is not populated. I remember we had this issue at one point. Forgot how we resolved that. You will not face that issue if you put this in beforeAll however.

[brdandu]

Do we need a chip repo and alchemy repo issue for CSA to start adding this to our existing XML?

[ethanzhouyc]

Alchemy can generate apiMaturity="provisional" when regenerating the entire ZAP XML. However, since the ZAP XML is too outdated for an entire update and only 22 clusters are marked as provisional in the CHIP repo, a manual update is more practical. Would you like me to create a PR for this?

[ethanzhouyc]

@brdandu According to my research, Jest runs tests sequentially within a single test file. Since all async functions use await, the first test will always complete before the second runs. The issue you mentioned would only occur if the variable were shared across different test files, as Jest runs test files in parallel.

In this case, both beforeAll and a separate test would work. I prefer keeping it in a test to allow expect() assertions, making potential setup issues easier to trace.