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): make fetching view for all mapped nodes optional #3686

Merged
merged 9 commits into from
Sep 12, 2023

Conversation

Savokr
Copy link
Contributor

@Savokr Savokr commented Sep 8, 2023

Type of change

Feat

Description 📝

Makes fetching view for all mapped nodes optional and accessible via parameter in exposed hook.

How has this been tested? 🔍

In HighlightNode story by adding the following code in StoryContent:

const { data } = useMappedEdgesForRevisions(
    [{ modelId: 2231774635735416, revisionId: 912809199849811 }],
    true
  );

  useEffect(() => {
    console.log('MappedEdges', data);
  }, [data]);

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.

@Savokr Savokr added auto-update Makes bulldozer automatically update this PR when there are changes to the target branch slack PRs and issues with this label will be pushed to Slack labels Sep 8, 2023
@Savokr Savokr requested a review from a team as a code owner September 8, 2023 14:43
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.

LGTM 👍 A couple of nitpicks

@Savokr Savokr enabled auto-merge (squash) September 11, 2023 10:23
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.

LGTM 👍

@Savokr Savokr merged commit bdd5bdd into master Sep 12, 2023
14 checks passed
@Savokr Savokr deleted the savokr/make-view-fetching-optional branch September 12, 2023 07:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-update Makes bulldozer automatically update this PR when there are changes to the target branch slack PRs and issues with this label will be pushed to Slack
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants