fix(typescript): allow objects while creating actions

[jkeam]

When creating actions, you can pass in an object literal (DefaultActionTypes). However, the typescript definition incorrectly didn't allow this. This PR addresses that.

This bug was found by @vinipachecov and reported here: #92
And by @sayjeyhi and reported here: #89

[vinipachecov]

I've made the changes you did in my current version "reduxsauce": "^1.1.1".

But it wasn't enough to fix some of the actions described in the docs:

• action with default values:
  
• custom action:
  

What I changed to make it work:

  export interface Actions {
    [action: string]: (string[] | DefaultActionTypes | CustomActionType) | null;
  }

  export interface DefaultActionTypes {
    [action: string]: string | null;
  }

 export type CustomActionType = (...a: any) => {[key:string] : any}

I know it is awkward the use of any, but since this is a custom action, it makes sense to me that the function should be able to receive all possible types, and the same would apply to the object returned, but it should be an object in end.

[jkeam]

Happy New Years @vinipachecov! Thanks again for your help with this issue. I just updated the PR. Can you give this a go and see if this solves your use case?

[vinipachecov]

Happy New Years @vinipachecov! Thanks again for your help with this issue. I just updated the PR. Can you give this a go and see if this solves your use case?

I'll give it a try today. I've been working during the new year's eve and during Christmas so until tomorrow I'll reply here.

[vinipachecov]

Worked fine here @jkeam , I think this is ready to merge :D

[jkeam]

🎉 This PR is included in version 1.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀