-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an info which group an applied template is associated with #636
Comments
As an alternative, I could also see the name being prefixed by the group/category label. That would result in the same output as it is now, it only takes the string from 2 sources: |
Is this a duplicate of bpmn-io/element-templates#8? |
Or it's rather a consequence of the basic support that has to be added via bpmn-io/element-templates#8 (adding the |
I'll mark it as depends on. |
We should discuss if we want to have it separately; but I guess it makes sense on the first glance. |
what you mean with separate @nikku ? separate like in the issue summary (having separate labels and description for group, name and description) and in contrast the compact variant like @jurgenhaas suggested? |
Is your feature request related to a problem? Please describe
Currently the info section for an applied template contains the name and the description of the template. Now the group functionality for the element template chooser has landed in bpmn-io/element-template-chooser#5 . Before the group functionality has landed the group name had to be prepend the template name (e.g. Tamper: Copy, Tamper: Format string - and that are only short examples with a single word group name). Template names are long and hard to scan and understand that way - with groups that prepend is not necessary anymore.
Describe the solution you'd like
in the template section for an applied template it could be simply added the info about which group a template belongs to.
before:
after:
Depends on bpmn-io/element-templates#8
The text was updated successfully, but these errors were encountered: