buchananwill

I agree that this part of the API is extremely counter-intuitive. This is a more generic hook version I use to fix it: ``` const fixProps = usePopoverFix(); { return...

This is one of the additions I will be including in the upcoming split pull requests. Example output: ``` export const CycleSubspanWithJoinsListDtoSchema = zod.object({ id: zod.number().int(), timeSpan: zod.lazy(() => TimeSpanDtoSchema),...

Ah, yes I've just noticed a nuance I should correct from this implementation actually - I didn't intend to allow number keys. The Typescript Generator converts all keys to `string`,...

I've just done a migration from v11 to v12, and I had some head-scratching with the Types for NodeProps. ### v11 Before the update, I might have a node component...

I have worked through this problem myself with V11. It was quite tricky to get all the interactivity to play ball. I'm about to update v12, so once I've checked...

I've copied over the simplest solution I found to get the node dragging to function correctly with d3 force layouting. Here's my fork of the example repo: https://github.com/buchananwill/quizzical-lamarr-tv8srd.git The gist...

I observed all of these behaviours as well, both in the example site, and my own project. The solution I posted is how I fixed it in my own project,...

Ah, you're right. I checked against my main project I copied from and I'd missed one detail: the current drag position needs to come directly from the ref, not the...

Please try the codesandbox again and let me know if it works for you now!

:-) you're welcome! On Mon, 23 Sept 2024, 19:32 Hebi Li, ***@***.***> wrote: > Awesome, it works! Thanks for the quick response and debugging. > > — > Reply to...