Hi,
Is it possible to remove the Orange Error when a User Text Key is not present on a Model Object? I am using the ‘Filter Content’ component to break up my data streams and most of the objects do not contain all possible set of keys. I think the warning is good, but making it my component orange is also makes my cluster orange when there is no real issue.
bump
any chance of considering this?
I’ve discussed this with @kike, and we both feel that a warning on the User Text component is the most appropriate message level for this issue (i.e., a key/value not being defined on an object). That said, if there is significant feedback or concern, we’re happy to revisit and discuss further.
I see. Is there any way of making it such that the error warning does not percolate outside into the cluster?
Here’s a small example of two components that have error warnings - one orange and one red -
cluster warning not shown.gh (8.8 KB)
and neither of them percolate error warnings outside
…to be honest I am not sure if I like this either because my script clearly isn’t working and there is actually no way to figure out why this is happening,. The way that a warning percolates outside a cluster is not consistent for components.
The only way to figure out why a null appears is to hover over the cluster and see the small snippet
But this is also not good when the snippet might be huge and lets be honest, I am not going to understand much when I work with 100s of clusters across dozens of files.
Hmm. If the cluster color is not being transferred correctly and/or consistently, then this sounds like a bug that I will need to investigate. I have created a YT ticket (RH-91101) to track this issue. If you have other examples of clusters which do not transmit the proper warning/error color to the cluster, please attach them here. Those would be useful in testing.
