Update rules for step definitions methods

[SamJ26]

The Step Definition Methods Rules section states that "method can not have a return type or have a Task as return type". I tried to change my method to return int instead of void and it works without errors. So I guess if it's not a rule which would cause an error than it should be rather recommendation than rule.

If it's a bug that SpecFlow should catch, I can provide you steps to reproduce it (although it's a very simple 😀)

Types of changes

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• Performance improvement
• Refactoring (so no functional change)
• Other (docs, build config, etc)

Checklist:

• I've added tests for my code. (most of the time mandatory)
• I have added an entry to the changelog. (mandatory)
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[SabotageAndi]

Yeah, we don't enforce this rule. If it is not a Task, we simply ignore the return type.

Thanks for your contribution to SpecFlow.
Please submit your contributions to our SpecFlow Community Heroes program at https://specflow.org/community/submit-a-contribution/