IDescriptionNameGenerator for downstream applications

[amontagne]

Hello

We're developing a downstream application based on a library of Definitions loaded at the application startup along SysML and KerML libraries. In our NodeProviders we would like to be to use IDescriptionNameGenerator to deduce names without having a specific EClass (one EClass matches several of our Definitions and therefore several node names). Would it be possible to move up the methods introduced in DescriptionNameGenerator up to the interface (such as getCompartmentName(String prefix, String suffix )?

And by the way thank you for the 2025.12.0 release (and its precious change notes), I really like how you extracted the code from the frontend into components (it definitely made our frontend more maintenable).

Anne-Lore

[AxelRICHARD]

Hello,

Thank you.

All protected methods coming from DescriptionNameGenerator are not used in SysON except in DescriptionNameGenerator itself.
So I don't understand why you want to add them in the IDescriptionNameGenerator interface.
Unless I'm missing something, It won't change anything for you.
If you want to override the behavior of those protected methods you can develop your own version by extending DescriptionNameGenerator.
Wouldn't it be enough for your needs?

Regards,

[amontagne]

Syson provides NodeDescriptionProviders with a IDescriptionNameGenerator protected field (or the getter itself is protected). We extend these NodeProviders for our own needs, and we can't use this field (as the mentionned methods are missing from the interface). We need the protected methods coming from DescriptionNameGenerator as we do not use the EClass to find out the name.
(Currently we add an extra field to use our NameGenerator directly instead of the interface).

[AxelRICHARD]

Ok I understand now, I will add the methods to the interface If it can help you.

Regards,

[amontagne]

Thank you!