David Sheldrick
David Sheldrick
this happens when the arrow bind point ends up outside of the outline, which can happen with cloud shapes because their outlines are dynamic.
Hello, thanks for the bug report! I'm sorry you encountered this issue. I suspect it's some kind of rendering problem, but we can't seem to reproduce it on our devices....
Yeah we no longer persist the `propsForNextShape` when stashing instance state. It could be done pretty easily. Shall I do it?
I think the message is pretty clear at this point...
@tgriesser See the section of the readme under the heading 'ES6 Map/Set inspired interfaces'.
@hipstersmoothie happy to. I don't see a convenient place to mention it, can you point me in the right direction?
> The only way to use this option right now would be by using auto programmatically which you probably don't want. On the contrary! The only reason we need this...
We are also using the socket hibernation api.
in case anybody else needs it, here is the script I wrote to wrap wrangler and restart it after a segfault. `dev.ts` ```ts import { ChildProcessWithoutNullStreams, spawn } from 'child_process'...
Not sure about adding version range constraints inside the file name. I'd be happy to accept a PR to add a cli option that prevents the mismatch warnings from being...