Improve AsyncActionCreator type signature to handle optional cancel property correctly

[piotrwitek]

Is your feature request related to a real problem or use-case?

Fix cancel is never #152

Describe a solution including usage in code example

Improve the resulting type signature of AsyncActionCreator making it more consistent with the rest of the API surface and to handle optional cancel property correctly.

The resulting signature must be looking like this:

AsyncActionCreator<["FETCH_USERS_REQUEST", undefined], ["FETCH_USERS_SUCCESS", User[]], ["FETCH_USERS_FAILURE", Error], ["FETCH_USERS_CANCEL", string]>

Who does this impact? Who is this for?

All

Describe alternatives you've considered (optional)

---

IssueHunt Summary

Sponsors (Total: $40.00)

• issuehunt ($40.00)

Become a sponsor now!

Or submit a pull request to get the deposits!

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[issuehunt-oss]

@issuehunt has funded $40.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[piotrwitek]

blocking because there is a significant amount of changes in the next branch (currently heavily WIP) that needs to be completed before possible to fix that. There is also a pretty high chance it will be fixed by #143

[piotrwitek]

Resolved by #194