This repository was archived by the owner on Dec 5, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 228
Feature: Propagate scheduleUpdate through nested poppers #121
Labels
Comments
I'd ask you to hold on on this feature because we are going to replace the API completely in the next few days (see #117). Anyway it's a good idea. |
I could perhaps base my PR on the |
I'm not sure if we are going to use that specific API or a mixture of the first iteration and the last one. |
The new API is now on beta and merged to |
Ok, I'll need about 1 day I think. When is v1.0.0 set to release? |
I'm waiting few days to receive feedbacks, if everything is fine I'll release it then. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When
scheduleUpdate
is called on a popper, it should callscheduleUpdate
on all nested poppers. We can do this through context so it works through portals, too.I'd be happy to take this on.
This would fix this issue: palantir/blueprint#2031
The text was updated successfully, but these errors were encountered: