change inference behaviour in old TS versions

[phryneas]

This should solve #165. I've added a new test and tested it with TS 3.5 and 3.3 (where it failed before this commit).

Feature-detecting TS<3.5 and handling it differently may not be the most elegant solution, but honestly, I don't have any better idea.

[netlify]

Deploy preview for redux-starter-kit-docs ready!

Built with commit 5e215ed

https://deploy-preview-166--redux-starter-kit-docs.netlify.com

[markerikson]

@phryneas : can you rebase this on latest master?

[phryneas]

I'll put it on the todo list :)

[phryneas]

@markerikson okay, based on the current master now.

On a completely unrelated note, because I noticed it just now: Shouldn't we commit a yarn.lock or package.lock?

[markerikson]

Uh... there is a package-lock.json already.

(I personally much prefer Yarn, at least for app usage, but Redux and React-Redux are on NPM, so I kept that for consistency.)

[phryneas]

Uh... there is a package-lock.json already.

(I personally much prefer Yarn, at least for app usage, but Redux and React-Redux are on NPM, so I kept that for consistency.)

Yup. I am blind. I'ts official now. 🤣

[markerikson]

Awright, let's throw this in there.