Skip to content
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.

Modify ConnectionEvents to specify both endpoints, and implement many to many connections #30

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Modify ConnectionEvents to specify both endpoints, and implement many to many connections #30

wants to merge 3 commits into from

Commits on May 26, 2022

  1. Have ConnectEventEnded specify both endpoints

    @gmorenz
    gmorenz committed May 26, 2022
    Configuration menu
    Copy the full SHA
    997c4d3 View commit details
    Browse the repository at this point in the history

  2. Make DisconnectEvent specify both endpoints

    @gmorenz
    gmorenz committed May 26, 2022
    Configuration menu
    Copy the full SHA
    1e76f94 View commit details
    Browse the repository at this point in the history

  3. Many to many connections 

    Currently graph connections are always one output to many inputs. This
is appropriate for most "data type values", but not always correct. The
motivating example for a place where it is incorrect is "control flow",
where many nodes might "output" control flow to the same node's control
flow input.

This changes that so that it is configurable via data-type whether nodes
are one-many, many-one, many-many, or even one-one with the concept of
splittable data-types (data types that can be copied from one output to
many inputs) and mergeable data-types (data types that can accept many
outputs into a single input).
    @gmorenz
    gmorenz committed May 26, 2022
    Configuration menu
    Copy the full SHA
    2b1028a View commit details
    Browse the repository at this point in the history