If (🚫Deprecated)(If)
If (🚫Deprecated) is a legacy node from the ComfyUI-Easy-Use package, now located in the EasyUse/🚫 Deprecated category.
If
Description
If (🚫Deprecated) is a legacy node from the ComfyUI-Easy-Use package, now located in the EasyUse/🚫 Deprecated category. The upstream source code no longer provides a description or docstring for this node. The input names (any, if, else) suggest that this node was originally intended as a ternary/conditional selector: a value supplied to any would be evaluated, and the node would return either the if or else branch. In the current deprecated state, however, all three inputs are exposed as required COMBO controls and the output type is reported as unknown, so this node should be treated as a compatibility shim rather than a functional logic node.
Inputs
- any (required, COMBO): A combo/dropdown input. The exact selectable values are not listed in the source metadata. Based on the parameter name, this was originally the value on which the
if/elsedecision would act. - if (required, COMBO): A combo/dropdown input. The exact selectable values are not listed in the source metadata. Based on the parameter name, this was originally the value returned when the condition was truthy.
- else (required, COMBO): A combo/dropdown input. The exact selectable values are not listed in the source metadata. Based on the parameter name, this was originally the value returned when the condition was falsy.
Outputs
- UNKNOWN: The node declares a single output of unknown type. Because the node is deprecated and no functional docstring is available, the output should not be relied upon to carry meaningful data in current workflows.
Usage Notes
- This node is marked 🚫 Deprecated and should not be used in new or active workflows.
- It may still appear in older saved workflows so that those graphs load without missing-node errors. Replace it with a current conditional, routing, or logic node from
ComfyUI-Easy-Useor with a native ComfyUI primitive/logic node if branching behavior is needed. - The absence of a docstring, combined with the
COMBOinput type on all three parameters, suggests that the implementation has been reduced to a placeholder. Use it only for backward compatibility, not for actual data flow.
Comments
Sign in with GitHub to join the discussion.