Skip to content
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

feat(react-components): fdm support in rule based core #4706

Merged
merged 39 commits into from
Aug 28, 2024

Conversation

danpriori
Copy link
Contributor

@danpriori danpriori commented Aug 17, 2024

Type of change

Feat

Jira ticket 📘

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

Description 📝

Initial FDM support in Rule Based core.
For now it supports: regular string, numeric, datetime and boolean expressions.

How has this been tested? 🔍

It was tested by overwriting any ruleset created in the project with FDM rule object. The reason for that is to avoid breaking the Set Threholds in 3d Management and the Search UI with the new FDM rule set content which needs some new type definitions and logic. So the safest was to test locally overwriting the saved rules with FDM object content by hand.

Test instructions ℹ️

One way to test is to paste the content of a FDM rule object in the file:line RuleBasedOutputsButton.tsx:93 right after the const selectedRule. You can use the example in the file below (one rule works in cog-3d and another in cog-demo).

fdm-test2.json

Or this example with two rules in cog-demo and another one in cog-3d:
fmd-test3.json

Screenshot 2024-08-19 130059

Note: it works with the PR: https://github.com/cognitedata/fusion/pull/7676

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.

Copy link
Contributor

@haakonflatval-cognite haakonflatval-cognite left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few comments

@danpriori danpriori merged commit 4b456b9 into master Aug 28, 2024
14 checks passed
@danpriori danpriori deleted the danpriori/BND3D-4440-fdm-support-in-rule-based-core branch August 28, 2024 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants