Hi everyone!
I’d like to suggest an improvement to how the **getParameterResolveOrder**
function (in packages/workflow/src/NodeHelpers.ts
) handles parameter dependencies.
Current Behavior
This function determines the order for processing node parameters based on their dependencies and **displayOptions**
.
When misconfigurations occur, especially circular or broken ones, it throws this error:
"Could not resolve parameter dependencies. Max iterations reached!
Hint: If displayOptions are specified in any child parameter of a parent collection or fixedCollection, remove the displayOptions from the child parameter."
This is helpful but still vague, making debugging difficult, especially for those building custom nodes.
Expected Behavior
It would be great if this could:
- Provide clearer, more targeted error messages.
- Warn about broken or circular dependencies earlier (e.g., in the editor).
- Suggest where the issue might be.
Improved handling would help developers catch issues faster, reduce debugging time, and make custom node creation more user-friendly.
Looking forward to your thoughts!