31479cfaa4
* [ADF-4152] Moved proc services cloud docs to subfolders * [ADF-4152] Fixed links in PS cloud docs * [ADF-4152] Added subfolders and checked links for extensions and insights docs * [ADF-4152] Moved proc services cloud docs to subfolders * [ADF-4152] Fixed links in PS cloud docs * [ADF-4152] Added subfolders and checked links for extensions and insights docs * [ADF-4152] Fixed links in Proc cloud, Insights and Extensions docs * [ADF-4152] Updated links in user guide * [ADF-4152] Fixed broken links in tutorials * [ADF-4152] Fixed remaining links in core docs * [ADF-4152] Fixed remaining links in proc services docs * [ADF-4152] Fixed remaining links in content services docs * [ADF-4152] Fixed links in breaking changes docs * [ADF-4152] Updated main README index page * [ADF-4152] Fixed glitches with preview ext component docs
1.9 KiB
Title, Added, Status, Last reviewed
| Title | Added | Status | Last reviewed |
|---|---|---|---|
| Dynamic Component | v3.0.0 | Experimental | 2018-12-17 |
Dynamic Component
Displays dynamically-loaded extension components.
Class members
Properties
| Name | Type | Default value | Description |
|---|---|---|---|
| data | any |
Data for the dynamically-loaded component instance. | |
| id | string |
Unique ID string for the component to show. |
Details
Use the Dynamic component to create extensible apps
(ie, apps that provide a generalized UI structure where the specific content
can be "plugged in" by other developers). The id property refers to a
component that has previously been registered using the setComponents method
of the Extension service:
// Registering the extension components.
extensionService.setComponents({
'plugInName.components.docList': DocumentListComponent.
'plugInName.components.login': LoginComponent,
...
});
<!-- Using the component pre-registered with the key 'plugInName.components.login' -->
<adf-dynamic-component
id="'plugInName.components.login'"
data="{ ... }"
>
</adf-dynamic-component>
Use this to provide the extension developer with a standard layout that
contains placeholders defined by instances of the Dynamic component. The
developer can then register any desired components to correspond to the
defined component IDs. For example, the extensible app might be shipped
with the standard Document List component registered against plugInName.components.docList.
The extension developer can replace this with a custom class
simply by registering that class with setComponents before use.