OptionalparamsSpecifies parameters required by the dialog.
Parameters can be read in the microfrontend by injecting the WorkbenchDialog handle, or referenced in path, title and resolvers using the colon syntax.
Arbitrary metadata associated with the capability.
Optionalclosable?: booleanSpecifies if to display a close button in the dialog header. Defaults to true.
OptionalcssClass?: string | string[]Specifies CSS class(es) to add to the dialog, e.g., to locate the dialog in tests.
Optionalpadding?: booleanControls if to apply a padding to the content of the dialog.
By default, dialogs provided by the workbench host application have a padding, others do not.
Specifies the path to the microfrontend.
The path is relative to the base URL given in the application manifest, or to the origin of the manifest file if no base URL is specified.
Path segments can reference capability parameters using the colon syntax.
{
"params": [
{"name": "id", "required": true}
],
"properties": {
"path": "products/:id", // `:id` references a capability parameter
}
}
Optionalresizable?: booleanSpecifies if the user can resize the dialog. Defaults to true.
Optionalresolve?: { [name: string]: string }Defines resolvers for use in the dialog title.
A resolver defines a topic where a request is sent to resolve text or a translation key, typically based on capability parameters. Topic segments can reference capability parameters using the colon syntax.
The application can respond to resolve requests by installing a message listener in the activator. Refer to ActivatorCapability for registering an activator.
OptionalshowSplash?: booleanInstructs the workbench to show a splash, such as a skeleton or loading indicator, until the dialog microfrontend signals readiness.
By default, the workbench shows a loading indicator. A custom splash can be configured in the workbench host application.
Optionalsize?: WorkbenchDialogSizeSpecifies the size of this dialog, required if this dialog is provided by an application other than the workbench host application.
Optionaltitle?: stringSpecifies the title of this dialog.
Can be text or a translation key. A translation key starts with the percent symbol (%) and may include parameters in matrix notation for text interpolation.
Text and interpolation parameters can reference capability parameters and resolvers using the colon syntax. See resolve for defining resolvers.
{
"params": [
{"name": "id", "required": true}
],
"properties": {
"title": ":productName", // `:productName` references a resolver
"resolve": {
"productName": "products/:id/name" // `:id` references a capability parameter
}
}
}
{
"params": [
{"name": "id", "required": true}
],
"properties": {
"title": "%product.title;name=:productName", // `:productName` references a resolver
"resolve": {
"productName": "products/:id/name" // `:id` references a capability parameter
}
}
}
Qualifies this dialog. The qualifier is required for a dialog.
Represents a microfrontend for display in a workbench dialog.
A dialog is a visual element for focused interaction with the user, such as prompting the user for input or confirming actions. The user can move and resize a dialog.
Displayed on top of other content, a modal dialog blocks interaction with other parts of the application. A dialog can be context-modal or application-modal. Dialogs are stacked per modality, with only the topmost dialog in each stack being interactive.
The microfrontend can inject the WorkbenchDialog handle to interact with the dialog, such as setting the title, reading parameters, or closing it.
Dialogs provided by the workbench host application have a footer and resize to fit content. See the documentation of
WorkbenchDialogServicein@scion/workbenchfor more information on adding actions to the footer.Dialogs provided by other applications must specify an explicit size in WorkbenchDialogCapability.properties.size and add the footer in the microfrontend.
See