Use correct FunctionalExchange styleclass on OA #377
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Wuestengecko
reviewed
Feb 5, 2024
Wuestengecko
changed the title
For styling reasons, we need to be able to distinguish between an FunctionalExchange that's on the operational layer and one that's not. We now simply call FEX on OA "OperationalExchange". This reactivates a (currently unused) symbol factory that produces orange tinted FEX symbols.
Wuestengecko
force-pushed
the
fix-functional-exchange-styleclass
branch
from
dd364a0 to
a65ea80
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
FunctionalExchanges in OA diagrams are not styled correctly. This is caused by a faulty/missing styleclass factory and aird factory patching the style class toOperationalExchange.Additionally missing default styles were added.