BUG: Any update on fixing the name space clashes in code blocks between OOTB nodes and Orchid package etc

[MattGaydon]

If this issue is not a bug report or improvement request, please check the Dynamo forum, and start a thread there to discuss your issue.

Dynamo version

Dynamo Version 2.1.0.7500
Revit Version 2.1.0.7733

Revit version

Revit 2020
20.0.0.377

Operating system

Windows 10

What did you do?

Node to code/ write a code block

What did you expect to see?

Working code block without requiring adding DsCore etc in front list say.

What did you see instead?

Broken Node

[ZiyunShang]

Hi @MattGaydon , I think you could ask Dynamo team for help about this issue - https://github.com/DynamoDS/Dynamo/issues

BTW, are you experiencing this issue in latest version of Dynamo?

[chuongmep]

I have same problem this when i install more package, i can fix quickly with call NameSpace before node.

[mjkkirschner]

This is not a "bug" per se - there is an existing mechanism which maps names to fully resolved types - it's not obvious, editable, or visible. Thats the first thing we will improve, but it's not on our roadmap at this point.

@aparajit-pratap may have more details on recent changes here - I think we made some improvements to the error messages present here, but no changes to the elementResolver (that is the component which maps shortNames to fully qualified type names)

[aparajit-pratap]

We have made a number of improvements to this issue recently: #10558. These will be available in Dynamo 2.7.