Singleton / lazily loaded dialogs with app-level triggers #2
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Dialogs are currently only accessible from a page that directly includes the component in its code. Some apps would benefit from optionally being able to define top-level "singleton" dialogs that can be triggered from any page and are lazily loaded as necessary. Consider implementing a top-level "dialog router" feature with context-based API that can be accessible from any page or layout below a top-level include. This would allow apps to trigger dialogs from any page as necessary, but also requires that dialogs manage state very carefully.