Skip to content

Conversation

@ivaylo-matov
Copy link
Contributor

Purpose

PR aims to address DYN-7844.

Overview
This is a proposal for new functionality that allows users to freeze an entire group from the group's context menu. This action freezes all nodes inside the group, including those within nested groups. Additionally, users can individually freeze/unfreeze nodes within a frozen group.

Behavior :

  • Freezing a group automatically freezes all nodes inside it, including nested groups.
  • Users can unfreeze individual nodes within a frozen group, but this does not unfreeze downstream frozen nodes.
  • Freezing a group affects downstream nodes outside the group.
  • This functionality also works with collapsed groups.

I've assumed including nested groups is within the expected behavior and that the context menu wording is acceptable. Please let me know if any adjustments are needed.

DYN-7844-Freeze groups

Declarations

Check these if you believe they are true

  • The codebase is in a better state after this PR
  • Is documented according to the standards
  • The level of testing this PR includes is appropriate
  • User facing strings, if any, are extracted into *.resx files
  • All tests pass using the self-service CI.
  • Snapshot of UI changes, if any.
  • Changes to the API follow Semantic Versioning and are documented in the API Changes document.
  • This PR modifies some build requirements and the readme is updated
  • This PR contains no files larger than 50 MB

Release Notes

This is a proposal for new functionality that allows users to freeze an entire group from the group's context menu. This action freezes all nodes inside the group, including those within nested groups. Additionally, users can individually freeze/unfreeze nodes within a frozen group.

Reviewers

@QilongTang
@reddyashish

FYIs

@dnenov
@achintyabhat

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

See the ticket for this pull request: https://jira.autodesk.com/browse/DYN-7844

@zeusongit zeusongit added this to the 3.5 milestone Mar 18, 2025
@zeusongit
Copy link
Contributor

@ivaylo-matov some conflicts

WorkspaceViewModel.DynamoViewModel.RaiseCanExecuteUndoRedo();
WorkspaceViewModel.HasUnsavedChanges = true;

Analytics.TrackEvent(Actions.Preview, Categories.GroupOperations, newFrozenState.ToString());
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we track analytics for freezing nodes, so this can be avoid for freezing groups as well.

Copy link
Contributor

Choose a reason for hiding this comment

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

We do have a Freeze Action, maybe use that instead of Preview

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you, both. The analytics is now tracking Freeze.

@reddyashish reddyashish merged commit 49bad52 into DynamoDS:master Mar 19, 2025
24 checks passed
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.

4 participants