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
Add info to the index prop documentation detailing the behaviour commented here, specifically regarding "we fire the onClose callback"
Why it is needed
It is somewhat counter-intuitive to invoke the onClose callback when the desired initial state of the bottomsheet is closed (index -1). The onChange callback can be used for tracking a explicit close event, so it's ok, but good for this to be clearly in the docs to avoid confusing over why onClose is being called when the user has no closed anything.
The text was updated successfully, but these errors were encountered:
this is weird behaviour, somehow onClose gets invoked initially when trying to open the sheet. After debugging for a hour.
Came up with this hack. It might be helpful for you.
Feature Request
Add info to the
index
prop documentation detailing the behaviour commented here, specifically regarding "we fire theonClose
callback"Why it is needed
It is somewhat counter-intuitive to invoke the
onClose
callback when the desired initial state of the bottomsheet is closed (index -1). TheonChange
callback can be used for tracking a explicit close event, so it's ok, but good for this to be clearly in the docs to avoid confusing over why onClose is being called when the user has no closed anything.The text was updated successfully, but these errors were encountered: