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.
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.
end
added the enhancement label 2026-06-16 10:28:47 -07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.