Alexander Mordvinov

I'm surprised this is still not implemented. Here's simple hack for those who need it. If you need to pass objects as data, add simple serialization-deserialization logic. ```tsx import {...

>Then this filtering can narrow down the type to a custom, more narrow type Yes I can narrow down middleware input context. But how to properly type context modified by...

> Using a type predicate. Look: Mutating inside filter is by any means ugly, I think you'd agree. But at least thanks for a workaround. > This code does not...

@KevinVandy Please just give us ONE of the hundred examples where the header is non-string and we will follow it. You either treat it as string or use `column.id`(for the...

You might find one here https://github.com/xyflow/xyflow/issues/4983#issuecomment-2800593465

> can you you try and remove your _build folder and go again Yep, that worked. Thanks! But still I think thats a bug. Before trying asdf I was facing...

Is it typescript or eslint error in your case? Now I'm getting `ESLint: Unknown property 'intensity' found(react/no-unknown-property)` for all the props, but it compiles ok. `"eslint": "^8.41.0",`

You sure the pull you mentioned is the right one?

Although explanation by @dberlin is really useful, I still don't think users have full control over renders. Consider this example: ```ts type NodeType = // Node-specific state { id: string;...

If i restructure my store such way: ```ts type NodeType = { text: string; flow: RequireFields< // React-flow specific Pick, 'type' | 'width' | 'height' >; }; const initialState: State...