refactor: split internal registries #2818
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In
BpmnElementsRegistry
, extract the remaining code that is not related to the management of BPMN elements.The code related to overlays has already been extracted and the new changes proceed in the same way for CSS classes and style update.
BpmnElementsRegistry
moved to other "registry" files. It is generally glue code :CssClassesRegistry
andStyleRegistry
GraphCellUpdater
, which generally does the real processing, is split into different updaters:CssClassesUpdater
andStyleUpdater
StyleManager
no longer depends onCssClassesCache
to reset styles. This make the "Style" and "CSS" API completely independent and will allow to fully split the registries in the future.In addition, apply refactoring to
OverlaysRegistry
for consistency with other registries.covers #2803
relates to #2800
Additional checks done to verify the implementation
Notes
Additional refactoring will follow to complete #2803 (interfaces extraction).