...
- Connecting it to a monitoring system agent (e.g. Elastic APM)
- Single sign-on (user authorization)
Decission
The use of OpenSCD addons
OpenSCD addons are an extension of OpenSCD-Core to split functionality. This functionality can be pure technical and requires no custom UI. Examples for some OpenSCD addons are Wizarding, Validating, Waiting, etc.
OpenSCD addons will be a replacement for current mixins, so there is no/less need to fork OpenSCD-Core and to build mixins on top of the fork. Addons allow experiments with (potential) new core functionality. Succesful addons can be merged into OpenSCD-core.
| Info | ||
|---|---|---|
| ||
Example: Wizarding API is hard to make pefect in the first run. If started with an addon for wizarding, we can experiment/use it. If it turns out that the addon is missing crucial functionality. We can introduce a new add-on next to the old addon (with its limitations). |
...
Pros
- It can use the current `plugin` mechanism to load.
Cons
- A background plugin is extending from `HTMLElement` but it's not rendering anything. This goes against the `CustomElement` principles.
- The dom can get polluted quickly by creating background plugins
Other alternatives: OpenSCD-core addon's alternatives
Conserquences
- `Addons` need to be loaded apart from `plugins`
- Risk of having addon's with similar functionality
...