Hello there @aehrenworth,
totally agree with you. I like to have my flows documented and adding comment/label (file name) under File Readers helps once you get back to it after a while. Not to mention if you are working in a bigger organization and you are sharing workflows - in this case standardized node comments mean a lot. I would even go a step or two further and suggest a automatic comment for every node. Here are couple of comment rules I follow:
- File Readers (regardless of configuration method) to feature a file name
- File Writers also to have a file name
- DB Reader node to be without comment (and every other node I find obvious enough like Concatenate, Column Appender, Table Manipulator…)
- DB Connectors to have hostname and database name
- String Manipulation to have expression (if not to big; in that case either meaningful column name or couple of words on operation)
- Column Filter to have list of included columns (in case it’s too big then either empty or list of excluded column if small and can help)
- …
This helps me “read” workflow in general faster and some node specifics without going into node configuration. Of course I understand that this features would require some development and time as there are many many nodes…
Another step would be to besides default node commenting there is customized commenting where user or organization can setup rules for specific nodes or a set of nodes if not satisfied with default.
If I read well there is similar request here:
And there is some development on this matter here so check if it can help:
Br,
Ivan