Please Note:

1. Before submitting the PR, please review How to Contribute to Dynamo
2. Dynamo Team will meet 1x a month to review PRs found on Github (Issues will be handled separately)
3. PRs will be reviewed from oldest to newest
4. If a reviewed PR requires changes by the owner, the owner of the PR has 30 days to respond. If the PR has seen no activity by the next session, it will be either closed by the team or depending on its utility will be taken over by someone on the team
5. PRs should use either Dynamo's default PR template or one of these other template options in order to be considered for review.
6. PRs that do not have one of the Dynamo PR templates completely filled out with all declarations satisfied will not be reviewed by the Dynamo team.
7. PRs made to the DynamoRevit repo will need to be cherry-picked into all the DynamoRevit Release branches that Dynamo supports. Contributors will be responsible for cherry-picking their reviewed commits to the other branches after a LGTM label is added to the PR.

Purpose

While addressing a crash it was determined that there was a path that a null value could be returned when there was no null check, which could lead to other possible crashes. This PR is intended to guard against possible null returns leading to a crash. Note that it is not intended to make the code fully functional in the event of exceptional circumstances, just to guard against crashing.

This PR currently only addresses the first three levels after the initial CreateNodeFromShortName possible method null return. There is still another level (or more) of null checks needed to definitively handle the null possibilities, but it seemed that the changes were leading to diminishing returns. This work can be continued using the notes in the associated JIRA issue (QNTM-5426).

Declarations

Check these if you believe they are true

• The code base 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.

Reviewers

@aparajit-pratap

FYIs

@mjkkirschner