Open cliffordfajardo opened 1 year ago
I tried adding data
directly on the port objects and I get an error. It looks like its from Elkjs?
Maybe the elkjs library doesn't like port objects with data
property on them 🤔😢
reaflow
repotab1: npm run build:watch
tab2: npm run start
data
property to a node inside of the Port.stories.tsx
file:
Description
It would be useful if port objects supported the
data
property that Node and Edge's support (types.ts file). This would allow the user to add additional meta information about the portMotivation for feature
I have a device with 2 ports; 1 on the left and one on the right This port is connected to multiple other edges / nodes on the canvas from a user point of view
I'd like to be able to check
port.data
, which contains my own data, before modifying a port object. In the example below, I addedred-port
class to a port that I didn't intentionally intent to (the left red port in the image) I was doing something like this:then , realized after looking at my code, that the concept of
data
for port didn't exist.Having
data
on port objects, would allow users to conditionally operate on the portReferences