You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[X] Feature request
[ ] Documentation issue or request
[ ] Support request => Please have a look to the support pages of our website : http://m2doc.org/support/
Current behavior
Current services allow to display diagrams but not to return their name (to provide it as legend in the document).
Expected behavior
Define a service to easilly return a diagram name.
It shall be as easy as the existing service as for example asImageByRepresentationDescriptionName('System Architecture Blank').
Moreover, in the case of a loop on existing diagrams, it shall be able to get the name of each diagram.
For example:
For this to work in a loop, it means that the model element that represents an image should be enriched with a name (or caption, or title; And maybe some other relevant information, depending on what can be attached to diagrams and images in general, although I don't see any right now)
Then the synta would be
{ m:im.fit(500,400) } <-- produce the image
{ m:im.title } <-- produce the image title/name/caption/whatever
I'm submitting a...
Current behavior
Current services allow to display diagrams but not to return their name (to provide it as legend in the document).
Expected behavior
Define a service to easilly return a diagram name.
It shall be as easy as the existing service as for example asImageByRepresentationDescriptionName('System Architecture Blank').
Moreover, in the case of a loop on existing diagrams, it shall be able to get the name of each diagram.
For example:
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Provide image legend in generated documents
Environment
The text was updated successfully, but these errors were encountered: