Context
OpenSCD add-ons are add functionality to extend the core functionality. It allows to experiment (with out commit it directly to the core) and add functionality for just a small group of users. Once an add-on is used a lot and is considered stable, it can become a part of the core functionality.
Decision
We will use OpenSCD-core addons in order extend the OpenSCD-core functionality.
Consequences
Pro's:
Flexibility
Room for experimentation
Con's:
Risk of having 2 similar Addon's with similar functionality
Keep track of all the addon's
Considered alternatives
Keep using Mixins as done in OpenSCD monolith architecture.
Pro's:
- Already known
Con's:
- Mixins are extentions on the code (code depends on OpenSCD classes)
- New mixins are hard to merge back into OpenSCD-core
- Change of many OpenSCD-core variants (all with different mixins)
Build a permanent solution directly in OpenSCD core
In the alternative, the idea is to add all the functionality directly into OpenSCD-core.
Pro's
- Easy to use: one single repository with all the needed functionality
Con's
- No room for experimentation
- Limited flexibility (these are the only