Template categories + search

[nikku]

Replace options, including templates can now be optionally classified by category:

Also, an additional search meta-data allows to specify search terms not displayed through name, label or description.

---

Try it out via

npx @bpmn-io/sr bpmn-io/bpmn-js-connectors-extension#template-categories-search -c 'npm start'

Enable create/append anything modeling UX via a feature toggle.

[nikku]

@currandwyer I'd love to make basic grouping available to our users. Please have a look at this change and highlight and feedback potential improvements.

[currandwyer]

@nikku I think this looks great, particularly in this append anything context. I also expect that append anything is the direction of travel for our modeling UX, so this will be a nice feature to have. When this does happen, I suggest changing the title to "Append specialized element" or something like this, to be specific and precise about the purpose of the component.

I realize it's out of scope, but I think that adding the ability to filter would be nice to have alongside this.

I don't think it makes sense to launch categories until we have a higher number of specialized tasks to categorize. Categorizing the REST and SendGrid connectors is a lipstick on a pig solution. Rather than categorizing them, we should focus on shipping auth so that the auth configuration exists within the properties panel, as it should. Then we only have two connectors, not enough to categorize. In any case, the categories will work differently (for more higher order distinctions), and we mustn't confuse these different mental models so early on.

I think it is very important not to refer to connectors as templates. We must align on one word (whether it is connectors or integrations or whatever) to refer to these things. The element template is a part of the connector, but it's not the main thing. Introducing this additional technical language, which requires users to develop an understanding of our technical architecture, could be unnecessarily confusing.

[nikku]

Thanks for your comments, both of you.

I realize it's out of scope, but I think that adding the ability to filter would be nice to have alongside this.

Agreed @currandwyer.

I don't think it makes sense to launch categories until we have a higher number of specialized tasks to categorize.

Will see if we can get rid of the categories in the append connector scenario.

I think it is very important not to refer to connectors as templates.

Also agreed. We are free to choose whatever naming / group labels. We can either settle on "REST", "SendGrid" as generic names, not ship these names at all or incorporate template / connector as dedicated terms.

What would be your preference? We can both have a look and experiment later this week, too. @currandwyer

[nikku]

Updated to not show the category, unless provided in connectors mode:

---

Also updated the branch so it can be merged independently.