Open snowe2010 opened 9 years ago
This is a very good discussion point. The decision around this rule came about because we, the original authors, come from the camp of making code expressive enough to make comments unnecessary. Comments in the gem were unfortunately a necessity because of rdoc's implementation that we accepted. You should have the ability to disable this rule if your team finds prefers having comments provided as part of your step definition conventions.
IntelliJ nicely shows comments on steps from a feature file with a shortcut, yet if I add comments to the steps like so
I get a cuke_sniffer warning,
Commented code in Step Definition.
when in fact it is not code that is commented at all.