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
Hello, and thank you for the great work on this library!
I’d like to suggest adding an optional destroyOnClose property to the Drawer component. This would help in scenarios where resources associated with the Drawer need to be cleaned up upon closure.
Use Case
In my company, we frequently use Drawer components as form wrappers. Currently, after submitting or closing a form within a drawer, I handle the cleanup manually. This process involves resetting form states, which can get repetitive and error-prone. An optional destroyOnClose property would greatly simplify this by automatically unmounting the drawer content, ensuring a fresh state when reopened.
Proposed Solution
Add a destroyOnClose property that:
If true, unmounts the drawer content when closed.
If false or unspecified, maintains the current behavior.
Hello, and thank you for the great work on this library!
I’d like to suggest adding an optional destroyOnClose property to the Drawer component. This would help in scenarios where resources associated with the Drawer need to be cleaned up upon closure.
Use Case
In my company, we frequently use Drawer components as form wrappers. Currently, after submitting or closing a form within a drawer, I handle the cleanup manually. This process involves resetting form states, which can get repetitive and error-prone. An optional destroyOnClose property would greatly simplify this by automatically unmounting the drawer content, ensuring a fresh state when reopened.
Proposed Solution
Add a destroyOnClose property that:
Example API
Benefits
Thanks for considering this request! Let me know if I can provide more details or help in any way.
The text was updated successfully, but these errors were encountered: