Added If node and ability to link an Any output to a node input if cardinality matches
#8869
+175
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR includes a feature + bugfix for the new
Ifinvocation and its editor interoperability:Ifinvocation node (if) with:condition: booltrue_input: Optional[Any]false_input: Optional[Any>value: Optional[Any](withdefault=Noneto avoid persisted-session validation failures when omitted).AnyFieldcan be used as a source where cardinality is compatible (instead of being blocked), which allowsIf.valueto connect to typed inputs in the UI.Iftrue/false behavior and graph connectivityif_outputwhenvalueis missingAnyFieldsource compatibility and cardinality guardrails in UI connection typing.Why:
Ifoutput wiring.if_output.valuein persisted JSON.How:
Related Issues / Discussions
QA Instructions
Backend schema/output checks
IfInvocationOutput.valueis optional with defaultNone.UI connection behavior checks
Ifnode and connectIf.valueto a typed input (e.g. string input).SINGLE -> COLLECTION).Automated tests
Merge Plan
Checklist
What's Newcopy (if doing a release after this PR)