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

DYN-7038-Build-In-Packages-Duplicates #15315

Conversation

RobertGlobant20
Copy link
Contributor

Purpose

Fixing duplicate package nodes in Library and Add-ons section
When loading a package that contains the extra/layoutSpecs.json file the nodes were showing duplicate in the Library and in the Add-Ons section. Then the fix was adding to ElementType the missing ElementTypes.BuiltIn when is in theBuilt-In Packages directory.

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

Fixing duplicate package nodes in Library and Add-ons section

Reviewers

@QilongTang @saintentropy

FYIs

@BogdanZavu

When loading a package that contains the extra/layoutSpecs.json file the nodes were showing duplicate in the Library and in the Add-Ons section.
Then the fix was adding to ElementType the missing ElementTypes.BuiltIn when is in the Built-In dir.
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-7038

@RobertGlobant20
Copy link
Contributor Author

This is a screenshot showing the expected behavior when loading the DynamoATF package.
image

Copy link

UI Smoke Tests

Test: success. 2 passed, 0 failed.
TestComplete Test Result
Workflow Run: UI Smoke Tests
Check: UI Smoke Tests - net8.0

@QilongTang QilongTang added this to the 3.2.1 milestone Jun 17, 2024
@QilongTang
Copy link
Contributor

Re-running the PR check to validate again

@BogdanZavu
Copy link
Contributor

I tested this and it works as expected. There is a test for the layoutspec. We can improve on it or add a new one.

@saintentropy
Copy link
Contributor

@BogdanZavu I think we can improve the test but I would get this merged first. The test should be adding NodeModel based node to the Signed Package example. That is produced in another repo but should be easy to get adjusted.

@saintentropy
Copy link
Contributor

@QilongTang Looks like test pass on the second run correct?

@QilongTang
Copy link
Contributor

@QilongTang Looks like test pass on the second run correct?

Yup, https://master-5.jenkins.autodesk.com/job/Dynamo/job/DynamoSelfServe/job/pullRequestValidation/16190/ passed

@QilongTang QilongTang merged commit f1831f6 into DynamoDS:master Jun 17, 2024
23 of 25 checks passed
@QilongTang
Copy link
Contributor

@RobertGlobant20 Please cherry-pick

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