Over the years, Sparx has allowed us to suppress the rendering of the stereotype/metatype from an element etc.
On a diagram, in the browser etc.
From a consistency point of view, this should be made universal.
In this feature request, I'm specifically asking for this to be applied to the RefGUID return string.
Sparx has replied to a previous defect report that since (potentially) multiple metatypes can be returned by the same RefGUID dialog, the metatype/stereotype needs to be provided. This, in my view, is a spurious argument, since, in the other places where the suppression can be made, the same metaphor applies. It seems to me that if the modelling architect has made the decision to suppress the metatype/stereotype then they accept the consequences.
However, in the equivalent forum post, I'm asking the users to add any instances that they find where that consistency hasn't been applied yet.
Reported,
Paolo
NOTE: In our case, our stereotype names are abbreviated/encoded versions of the metatype name and so are of dubious values to our users. But that's only a special use case. The general principle still applies, regardless.
Modify message
