Idea: Check for usage of 'Name' instead 'DeveloperName'

[rogerhenze-web]

Thanks for this great tool btw. !
We have had issues, where the label of a queue (group) was modified, while a flow was checking on the queue's name rather than the queue's developer name. Same can happen, when using names of roles, public groups, record types, email templates etc. etc. where in flows you should prefer to use developer names (API names) instead of the names (labels).
Would be greate, if Flow Scanner could identify those as issue also.

[RubenHalman]

Hi @rogerhenze-web, thank you for the feedback.
I think this is a great suggestion for a new rule. While it may not be possible to cover 100% of all scenarios, it should definitely be feasible to detect cases where a Name field is used on metadata-type objects and flag those as potential issues.