passing type inference in trigger props? about nodes-io

[dmnsgn]

Thanks for the suggestion.

the editor allows for TypeScript annotations but the compiler doesn't...

They are indeed two different systems. The editor is currently spawned for each node so its doesn't have any understanding of other nodes, their ports and how they are connected but I agree that having types for props would be helpful.

the editor offers to move the JSDoc types to TypeScript types

I actually never noticed, but that's a default suggestion as the editor parses the code as TypeScript for enhanced experience (even though it is not).

[discohead]

the editor offers to move the JSDoc types to TypeScript types

I actually never noticed, but that's a default suggestion as the editor parses the code as TypeScript for enhanced experience (even though it is not).

Since the editor is able to correctly translate JSDoc types to TypeScript types, then maybe it's possible to enable the autocomplete/intellisense features from JSDoc types?

FWIW, VSCode can do exactly that...

[discohead]

I see that Nodes is using Monaco for its editor, there seems to have been some discussion around this here, though it's not clear to me where it ended up: microsoft/monaco-editor#203

However, a couple of relevant StackOverflow threads seem to indicate it should work in Monaco from v0.9.0...
https://stackoverflow.com/questions/39694407/adding-javascript-type-hints-for-vscode-monaco-intellisence

https://stackoverflow.com/questions/43037243/provide-type-hints-to-monaco-editor

No luck using @type either, but again the editor offers to move it to TypeScript and can do so correctly...

[discohead]

@dmnsgn just wanted to make sure you saw my comments above, from what I can tell, the monaco-editor in Nodes should be able to provide intellisense from JSDocs. This was added in Monaco 0.9.0, seems it does require some options/config in monaco, see: https://stackoverflow.com/questions/43037243/provide-type-hints-to-monaco-editor/45181853#45181853