You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing <Popper /> component doesn't feel right, it does absolutely nothing, if not allow the consumers to pass props down and retrieve the result.
The README example could be written as follows and everything would still work:
The idea is to wrap both actions in an object such that there is some shared state, then attach Popper there.
For my package, I have a createPopperActions function which returns two functions – refAction and popperAction, that are used on the reference and popper element.
popperAction takes the popper options config object, and while it doesn’t emit any event to update styles or attributes yet, that is definitely a possibility.
The existing
<Popper />
component doesn't feel right, it does absolutely nothing, if not allow the consumers to pass props down and retrieve the result.The README example could be written as follows and everything would still work:
A cleaner approach could be the
use:action
API.Here's a basic example:
https://codesandbox.io/s/trusting-butterfly-704gd?file=/popperAction.js
Thoughts?
The text was updated successfully, but these errors were encountered: