You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes a crash where, while creating a new Package, attempting to remove CustomNodeDefinitions from the current loaded list of files would result in unhandled "Sequence contains no matching element" error. This is happening because of the way we handle custom nodes with duplicate naming, constructing the Display Name using the [namespace].[node name] combination.
The PR addresses the underlying cause of the issue.
This PR modifies some build requirements and the readme is updated
This PR contains no files larger than 50 MB
Release Notes
fixed a crash where removing custom nodes with identical names would cause a null "Sequence contains no matching element" due to how we handle duplicate node names
- fixed a crash where removing custom nodes with identical names would cause a null "Sequence contains no matching element" due to how we handle duplicate node names
dnenov
changed the title
fixed a crash
PM - crash fix when removing custom nodes with identical names
Dec 2, 2024
dnenov
changed the title
PM - crash fix when removing custom nodes with identical names
DYN-7946:PM - crash fix when removing custom nodes with identical names
Dec 2, 2024
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Fixes a crash where, while creating a new Package, attempting to remove
CustomNodeDefinitions
from the current loaded list of files would result in unhandled "Sequence contains no matching element" error. This is happening because of the way we handle custom nodes with duplicate naming, constructing theDisplay Name
using the [namespace].[node name] combination.The PR addresses the underlying cause of the issue.
https://jira.autodesk.com/browse/DYN-7946
Declarations
Check these if you believe they are true
*.resx
filesRelease Notes
Reviewers
@jnealb
@QilongTang
FYIs