-
Notifications
You must be signed in to change notification settings - Fork 635
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
Update NodeModel nodes out port types #11631
Conversation
Update ColorRange and ColorPalette
@aparajit-pratap @mjkkirschner Please check this one out about my audit results. Especially about the undefined ones, is there a particular node you think output type should be defined? Let me know and I can update the PR |
I will fix the unit test and update PR again |
@@ -73,6 +73,7 @@ public override IEnumerable<AssociativeNode> BuildOutputAst(List<AssociativeNode | |||
[NodeName("Function Compose")] | |||
[NodeCategory(BuiltinNodeCategories.CORE_EVALUATE)] | |||
[NodeDescription("FunctionComposeDescription", typeof(Resources))] | |||
[OutPortTypes("Function")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aparajit-pratap should this have a namespace or the classes defined . ds files don't have namespaces?
@@ -317,6 +317,7 @@ public override void Dispose() | |||
[NodeCategory("Core.File")] | |||
[NodeDescription("DirectoryObjectNodeDescription",typeof(Resources))] | |||
[NodeSearchTags("DirectoryPathSearchTags", typeof(Resources))] | |||
[OutPortTypes("object")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't this be var
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mjkkirschner I updated to be consistent with file from path, see PR description. I think anyway object
seem to be made up, but I am not sure how many instances of that so I only make it consistent for now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but looking at the buildOutputAST
method for FileSystemObject<T>
- it looks like the correct return type is T
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I removed type object
and updated for three nodes
It looks like a good improvement to me @QilongTang - except shouldn't string input node return a string? |
It should but it seems an exception of regular node model node so I found no way to set the output type :( |
Please Note:
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 aLGTM
label is added to the PR.Purpose
As an alternative than #11621, do an audit to existing all NodeModel nodes and update their in/out port types. Due to Github crash, I lost all my notes for my progress in this PR of the ~50 nodes. Will update again tomorrow when I find the time.
Updated to
DSCore.Color
Remain as
var
Updated to
var
Remain as
dateTime
Remain as not defined
Remain as
List
Updated to
List
Updated to
List
,List
Updated to
number
Remain as
number
Remain as
int
Updated to
string
Remain as
string
Remain as
bool
Remain as
Function
Update as
Function
Removed type as
object
Remain as
type
Remain as
var[]..[]
Updated to
var[]..[]
Declarations
Check these if you believe they are true
*.resx
filesReviewers
@DynamoDS/dynamo
FYIs