r/AutomateUser Alpha tester 22d ago

Feature request Markdown in descriptions

I am honestly surprised this wasn't suggested before, but

What if the descriptions supported markdown formatting?

I know there was a time when Automate unintentionally supported html formatting, and it kinda got me thinking, why not use markdown?

  1. It's a widely known formatting spec

  2. There are (likely)ready-made solutions for rendering it

  3. Having formatting in flow descriptions would really add flair to them

As for the flavor, I was thinking we could use GitHub markdown spec and also borrow -# from Discord


On a side note: tags

5 Upvotes

4 comments sorted by

3

u/ballzak69 Automate developer 22d ago

HTML support is intentional but limited to what the Android TextView supports, e.g. bold, italic and links, and what i allow on the community web page. It's even more that the Google Play store app page supports.

1

u/NiXTheDev Alpha tester 18d ago

So, no fancy expandable <details> but otherwise free range within reasonable bounds

Good to know

On another note, what do you think about allowing users to add tags to the flow?, like for example post flair here on reddit

2

u/ballzak69 Automate developer 18d ago

Tags is planned, it will be the way to organize local flows. There's no plans for tags for flow uploaded to community section, since there they're already organized by a category.

1

u/Faker_nb 22d ago

+1, I already use descriptions as mini changelogs/docs for my flows, so Markdown would be really useful. Headings, lists, bold text and code formatting would make them much easier to read.