fix(react-components): filter undefined asset ids in rule based coloring when extracting unique asset ids

[danpriori]

Type of change

Jira ticket 📘

https://cognitedata.atlassian.net/browse/

Description 📝

With recent updates to the SDK, it may have affected the processing of IDs and you may be receiving undefined IDs when retrieving asset IDs from mapped. This small fix creates a filter to not return undefined IDs and therefore not request empty IDs from the getByIds endpoint.

Test instructions ℹ️

Checklist ☑️

• I am proud of this feature.
• I have performed a self-review of my own code.
• I have added PR type (Feat, Bug, Chore, Test, Docs, Style, Refactor) to the PR title.
• I have manually tested this for different scenarios (different models, formats, devices, browsers).
• I have commented my code in hard-to-understand areas.
• I have made corresponding changes to the public documentation.
• I have added unit and visuals tests to prove that my feature works to the best of my ability.
• I have refactored the code for readability to the best of my ability.
• I have checked that my changes do not introduce regressions in the public documentation.
• I have outlined any known defects / lacking capabilities in the contents of this PR.
• I have listed any remaining work that should follow this PR in the description or jira/miro/etc.
• I have added TSDoc to any public facing changes.
• I have added "developer documentation" in any package README.md that is related / applicable to this PR.
• I have noted down and am currently tracking any technical debt introduced in this PR.
• I have thoroughly thought about the architecture of this implementation.
• I have asked peers to test this feature.

[haakonflatval-cognite]

Looks good - but I'm wondering if this should perhaps not be a hook (I don't see why it should be a hook 😅 ), and then we could add a test to it, following current trend

[danpriori]

Looks good - but I'm wondering if this should perhaps not be a hook (I don't see why it should be a hook 😅 ), and then we could add a test to it, following current trend

Hmmm I think as this hook is calling some react hooks like useCallbacks or useMemos, for example, then it should be inside a hook, or a FC (ofc). In this case it is only useMemo.

About the tests, I was thinking to do the rule based coloring tests altogether in a unique cycle of writing tests as following the QA jira tickets for that. But I can write tests specific for this element to reduce the test workload later.

[haakonflatval-cognite]

LGTM 👍