Tristan
Tristan
Hmm, interesting idea! While I think about the appropriate implementation, you can quickly replicate this behavior with something like: ```js const [initialState, setInitialState] = useState(['some initial state']); const [state, setState,...
Nice, okay. I will update you when this option has been added.
+1 This also applies to the ReactFlow component being nested inside of a will-transform component like so: ``` import { motion } from 'framer-motion'; // ... ``` (The edges are...
I understand. Thank you for your response.
Increasing the handle size has always been a possibility. I'm mentioning new behavior that allows creation of an edge directly on a node, not only the handle—behavior that would be...
Could this have unintended side-effects for projects expecting a potentially `undefined` value? Why not create your own node `interface` with these requirements? Sure, some internal ReactFlow functions like `isNode`, for...
> I think it only has side effect for TypeScript projects during type checking / compilation. This is what I mean, yeah. TypeScript will only complain during type checking and...
Upon further analysis (and forgive my horrid delay here), I've decided not to implement this; I think there's too many conditions to be added here. For example, some projects may...
Hey @vallsv, I like this solution! I'm wondering if this achieves the same effect as the `ignoreAction` param on `setState`, however. Take a look at this [crude example I whipped...
No worries! Feel free to reopen it when you get back to it :)