I sorely miss a comment block. It makes future maintenance work much easier, as well as keeping a clear picture while in the creation phase. Making modifications in a flow I created some time ago can be challenging at times: trying to understand how things were done, what algorithms were used, meaning and usage of certain variables, etc... I've been programming for over 50 years (70 y.o. now), and the most valuable thing I learned at an early stage was documenting my work - for myself and for others. Trying to modify somebody else's undocumented program is often nearly impossible, resulting on many ocasions in rewriting it from scratch.
Same as Victor S., I created my own workaround by adopting another block, in my case the "Append log" block. For this to work without interfering in the real logging of the flow, do the following:
- First disactivate the "Logging" box in the main page of the flow (where all the privileges are listed)
- Insert your "Append log" block wherever you want to document something and activate its "Logging" field, setting it to "Only when logging enabled". This will avoid messing up the flow's log.
- When inserting an "Append log" block that you want to pass log messages to your log, make sure that its "Logging" field is disactivated.
The result is each Log block will display upto 28 characters without needing to open it (of course, you can write more as usual). This makes it easy to skim through your flows.
I prefer using the "Append log" block instead of the "Variable set" block because the icon displays more of my text, and looks cleaner. In any case, thanks to
Victor S. for his workardound, as this is what got me on the right path some months ago.
For the developer: PLEASE include comment block.