Jackson Hardaker
@jacksonhardaker.bsky.social
past jazz musician - current software engineer (@bitdrift.io)
That's right. We also use MUI as the underlying component library, xyflow for our workflow editor, and airbnb/visx for visual chart primitives .
May 9, 2025 at 3:06 PM
That's right. We also use MUI as the underlying component library, xyflow for our workflow editor, and airbnb/visx for visual chart primitives .
In that snippet the "ComparisonProvider.Treatment" context has access to the treatment tooltip position setter, and the control getter, while "ComparisonProvider.Control" has access to the control setter, and the treatment getter.
November 22, 2024 at 9:47 PM
In that snippet the "ComparisonProvider.Treatment" context has access to the treatment tooltip position setter, and the control getter, while "ComparisonProvider.Control" has access to the control setter, and the treatment getter.
🧵 4/4
End result looks something like:
End result looks something like:
November 22, 2024 at 9:06 PM
🧵 4/4
End result looks something like:
End result looks something like:
🧵 3/4
Problem 3: Expose the setter/getter to the relevant chart.
Solution: Add two variants of a nested context which exposes getter A / setter B, and getter B / setter A.
Problem 3: Expose the setter/getter to the relevant chart.
Solution: Add two variants of a nested context which exposes getter A / setter B, and getter B / setter A.
November 22, 2024 at 9:06 PM
🧵 3/4
Problem 3: Expose the setter/getter to the relevant chart.
Solution: Add two variants of a nested context which exposes getter A / setter B, and getter B / setter A.
Problem 3: Expose the setter/getter to the relevant chart.
Solution: Add two variants of a nested context which exposes getter A / setter B, and getter B / setter A.
🧵 2/4
Problem 2: Prevent changes in your new context propagating back to the chart component which dispatched the change.
Solution: Track the tooltip position for each chart separately, splitting the context to expose the setter/getter separately.
Problem 2: Prevent changes in your new context propagating back to the chart component which dispatched the change.
Solution: Track the tooltip position for each chart separately, splitting the context to expose the setter/getter separately.
November 22, 2024 at 9:06 PM
🧵 2/4
Problem 2: Prevent changes in your new context propagating back to the chart component which dispatched the change.
Solution: Track the tooltip position for each chart separately, splitting the context to expose the setter/getter separately.
Problem 2: Prevent changes in your new context propagating back to the chart component which dispatched the change.
Solution: Track the tooltip position for each chart separately, splitting the context to expose the setter/getter separately.