EndilWayfare
EndilWayfare
Ok, found something that works. Inspecting the target value of an `attrTween` is... involved. ```js import { isTransition } from "@d3fc/d3fc-data-join"; const getExistingAttr = (selection) => { if (isTransition(selection)) {...
Maybe `propagateTransition` should catch errors when trying to inherit? https://github.com/d3fc/d3fc/blob/b294f0a6f326b9eb001498e6760c0f0c8772620f/packages/d3fc-chart/src/cartesian.js#L48-L49 ```js const propagateTransition = maybeTransition => selection => { let selection = selection; if (isTransition(maybeTransition)) { try { selection =...
Extends to other places where transition inheritance happens, like in `dataJoin` https://github.com/d3fc/d3fc/blob/344b468a59bc4b939a99a3dda0b0ff0d0becc9f6/packages/d3fc-data-join/src/dataJoin.js#L46-L53
Yes, I've been digging through the source (both `d3fc` and `d3` itself) more since I posted, as well as fiddling with local copies of various components to investigate possible fixes/workarounds....
Hmm, so registering an event handler inside the outer `propagateTransition` closure, perhaps? Where would such a component live? It seems like `d3fc-data-join` package is the natural place, because that's generally...
Ah, ok. I think I understand. I suppose I misunderstood how the events are dispatched. Related: The `container` passed to decorate is not "transition propagated" https://github.com/d3fc/d3fc/blob/b294f0a6f326b9eb001498e6760c0f0c8772620f/packages/d3fc-chart/src/cartesian.js#L168 vs https://github.com/d3fc/d3fc/blob/b294f0a6f326b9eb001498e6760c0f0c8772620f/packages/d3fc-chart/src/cartesian.js#L118-L126 There seems...
Hmm, that's unfortunate. The app is designed to work locally, with data parsed client-side from file inputs. The server just serves an app bundle. Thanks for the suggestion! I'll keep...
**Update:** Ok, to be clear, that's the unoptimized dev build. Timing the release build is much less egregious, though still a noticeable hitch. I didn't think about this at first,...
Wow, @yannleretaille, you rock! Gotta love compile-time guarantees. :)
Ok, counter-argument might be ```rust fn foo(bar: impl Into) { unsafe { foreignFoo(bar.into().bits()) } } ``` is the most clear, compact way to delineate "convert compatible Rust type to `FlagSet`;...