Why? Sometimes your tool simply displays some info and the requirement for async generators is irrelevant.
Discussion:
Should we also support synchronouos generators?
I think not as this could lead to tons of unexpected mistakes.
Should we also support async render functions without generators?
We have the capability to easily add the support, but maybe we should intentionally leave it out to actively encourage developers to use generators to show current state of tool processing.
Pull-Request Checklist
[x] Code is up-to-date with the master branch
[ ] npm run lint passes with this change
[x] npm run test passes with this change
[x] This pull request links relevant issues as Fixes #0000
[ ] There are new or updated unit tests validating the change
[x] Documentation has been updated to reflect this change
Description of change
Fixes issue #12.
Why? Sometimes your tool simply displays some info and the requirement for async generators is irrelevant.
Discussion:
Should we also support synchronouos generators?
I think not as this could lead to tons of unexpected mistakes.
Should we also support async render functions without generators?
We have the capability to easily add the support, but maybe we should intentionally leave it out to actively encourage developers to use generators to show current state of tool processing.
Pull-Request Checklist
master
branchnpm run lint
passes with this changenpm run test
passes with this changeFixes #0000