Christopher Patty

@PhilGarb Thanks! This sounds like an intriguing use-case. If I'm understanding correctly, you'd want to leverage the node editor as more of a workflow modeling tool is that correct? Do...

Ah, that makes sense. It seems like there's a few missing pieces to make this kind of workflow possible. I would be worried that allowing users to edit the ports...

Also, with upcoming theming capabilities, the goal would be to make it possible to restyle the editor any way you like, including restyling nodes specifically based on their type. That...

Awesome! Yeah I'd love to get your feedback on the theming issue, the goal would be to make this use-case possible. I'm going to add both of these features to...

@andraz-at That sounds like a possible enhancement, but an API for it would need to be defined. If you open a separate issue for default connections I'll get it added...

This also came up in issue #29. Implementing a way to keep controls rendered when they're connected wouldn't be that hard to do I think. I'd like to hear more...

@numso I think a drag handle on each node to allow it to be resized at least horizontally is the right approach. That puts it in line with the comments...

This isn't currently possible, but to make it possible I think two features would be required: 1. **Theming**: Styles will need to be able to be dynamically applied based on...

Something in the timing must be a little bit off then. I'm getting the setState error when I use it like so: https://www.useloom.com/share/71f0474ebfd44a779cf0f3d4c9f44cf1

It's in the case where I have a `Droppapble` nested inside of another `Droppable`. The inner `Droppable` throws the error because it's only rendered while dragging, and unmounts immediately after.