Clarify that `Task` is a valid return type in Step - Githubissues

SpecFlowOSS / SpecFlow

#1 .NET BDD Framework. SpecFlow automates your testing & works with your existing code. Find Bugs before they happen. Behavior Driven Development helps developers, testers, and business representatives to get a better understanding of their collaboration

https://www.specflow.org/

Other

2.25k stars 754 forks source link

Clarify that `Task` is a valid return type in Step #2675

Closed bjarketrux closed 1 year ago

bjarketrux commented 2 years ago

The sentence "Shouldn't have a return type or have Task as return type." can be read in two ways:

Should not have a return type nor return Task
Should not have a return type OR should return Task

So a minor change to make it more clear and direct.

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)
[x] 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.
[x] I have updated the documentation accordingly.

SabotageAndi commented 1 year ago

Thanks for this change! It really makes it easier to understand.