Execution Model Inversion Guide

​

Breaking Changes

​

Monkey Patching

​

Optional Input Validation

• Use of reserved Additional Parameters like min and max on types that aren’t comparable (e.g. dictionaries) in order to configure custom widgets.
  • Change the additional parameters used to non-reserved keys like uiMin and uiMax. (Recommended Solution)
    @classmethod
    def INPUT_TYPES(cls):
        return {
            "required": {
                "my_size": ("VEC2", {"uiMin": 0.0, "uiMax": 1.0}),
            }
        }
    
  • Define a custom VALIDATE_INPUTS function with this input so validation of it is skipped. (Quick Solution)
    @classmethod
    def VALIDATE_INPUTS(cls, my_size):
        return True
    
• Use of composite types (e.g. CUSTOM_A,CUSTOM_B)
  • (When used as output) Define and use a wrapper like MakeSmartType seen here in the PR’s unit tests
    class MyCustomNode:
    
        @classmethod
        def INPUT_TYPES(cls):
            return {
                "required": {
                    "input": (MakeSmartType("FOO,BAR"), {}),
                }
            }
    
        RETURN_TYPES = (MakeSmartType("FOO,BAR"),)
    
        # ...
    
  • (When used as input) Define a customVALIDATE_INPUTS function that takes a input_types argument so type validation is skipped.
    @classmethod
    def VALIDATE_INPUTS(cls, input_types):
        return True
    
  • (Supports both, convenient) Define and use the @VariantSupport decorator seen here in the PR’s unit tests
    @VariantSupport
    class MyCustomNode:
    
        @classmethod
        def INPUT_TYPES(cls):
            return {
                "required": {
                    "input": ("FOO,BAR", {}),
                }
            }
        
        RETURN_TYPES = (MakeSmartType("FOO,BAR"),)
    
        # ...
    
• The use of lists (e.g. [1, 2, 3]) as constants in the graph definition (e.g. to represent a const VEC3 input). This would have required a front-end extension before. Previously, lists of size exactly 2 would have failed anyway — they would have been treated as broken links.
  • Wrap the lists in a dictionary like { "value": [1, 2, 3] }

​

Execution Order

​

New Functionality

​

Validation Changes

• Default validation will now be skipped for inputs which are received by the VALIDATE_INPUTS function.
• The VALIDATE_INPUTS function can now take **kwargs which causes all inputs to be treated as validated by the node creator.
• The VALIDATE_INPUTS function can take an input named input_types. This input will be a dict mapping each input (connected via a link) to the type of the connected output. When this argument exists, type validation for the node’s inputs is skipped.

​

Lazy Evaluation

​

Node Expansion