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
This is a formal issue to discuss the ideas in #1671
At the moment, each dialog service is associated with only a single dialog-dom-renderer. This means that applications may need to create multiple dialog services to produce different dialog dom structures. For example: one for notifications and one for modals, because notifications normally have a different DOM structure compared to modals.
This inflexibility is unnecessary, and it would be better if the dialog service could have different renderer for different occasions:
classMyApp{alert(){dialogService.open({renderer: modalRenderer,// render standard modal dom with overlay, host etc...
...
})}notify(){dialogService.open({renderer: notificationRenderer,// no need overlay
...
})}
bigopon
changed the title
rfc(dialog): ability to have specify renderer per open call
rfc(dialog): ability to specify renderer per open call
May 15, 2024
This is a formal issue to discuss the ideas in #1671
At the moment, each dialog service is associated with only a single dialog-dom-renderer. This means that applications may need to create multiple dialog services to produce different dialog dom structures. For example: one for notifications and one for modals, because notifications normally have a different DOM structure compared to modals.
This inflexibility is unnecessary, and it would be better if the dialog service could have different renderer for different occasions:
cc @ekzobrain
The text was updated successfully, but these errors were encountered: