Motivation behind deprecations

[Riduidel]

Hello, in the latest versions, some concepts have been deprecated or removed that I tend to use ... a lot ... in Aadarchi.

Namely

• CodeElement has been removed in v1.21.0, which is frankly a bad decision from my point of view
• Enterprise has been deprecated in v1.23.0
• Location has been deprecated in the same version

Could it be possible to discuss why these elements disappear (ideally before they disappear) ?

[simonbrowndotje]

• Code elements: these are not used by any of the core Structurizr tooling (the "component finders" haven't been supported for a few years now, and the Structurizr UI doesn't support rendering them), so I took the decision to remove them.
• Enterprise boundary and location: these concepts are too limited, so I recently added support for nested groups.

[Riduidel]

I understand the rationale behind CodeElement deletion, but as I'm using them (for various reasons), I'm a bit puzzled on how to emulate that feature (excepted by abusing the element properties)

[simonbrowndotje]

If I ever resurrect the component finder code, I'd probably just make my own CodeElement class in that library, along with a way to store them, perhaps something like Map<Component,Set<CodeElement>>.

[Riduidel]

Would you be interested if someone (like me) took care of that part ? Maybe I could try some kind of responsibility delegation.

[simonbrowndotje]

You are more than welcome to fork the component finder code and take it into your own repo ... I have enough other code to support. 😀

[Riduidel]

Isn't it already in structurizr extensions ? (where I'm a contributor)

[simonbrowndotje]

Closing this discussion in favour of structurizr/java-extensions#69.