Creating actions causing some problems about typesafe-actions HOT 11 CLOSED

Hi @abdurahmanus
From v2.0.4 both of your use-cases should work correctly: #48

// case 1)
const someAction = createAction('something', resolve => () => resolve(undefined, 'some meta info')); 
someAction() // { type: 'something'; meta: string; }

// case 2)
const someOtherAction = createStandardAction('somethingElse').map(() => ({
  meta: 'some meta info',
}))
someOtherAction() // { type: 'somethingElse'; meta: string; }

API documentation was updated with all the above examples of "meta only" cases.

Already released a new version to npm, enjoy!

PS: I'm closing this as all the mentioned cases are supported now, and the issue with strictFunctionTypes is already tracked in #44, so there's no need for duplication

from typesafe-actions.

also it would be helpful if we could create actions using createAsyncActions helper specifying the type of meta

from typesafe-actions.

Ad 1) this is a valid point, adding support for this case is easy, will need to update validation checks
Ad 2) not sure what you want here, it's how TS works, nothing actionable or related to the library

Regarding types issue it is related to react-redux@6 types, not in this library, please use react-redux@5 until there is a working solution: #42

To extend createAsyncActions API we need a proposal

from typesafe-actions.

I've tried react-redux types v5
this code

const ADD = 'ADD'

interface Todo {
  title: string;
  id: number;
  completed: boolean;
}

export const add = createStandardAction(ADD).map(
  ({ title }: { title: string }) => ({
    payload: { title, id: 12, completed: false } as Todo,
  })
);

still don't work

[ts]
Argument of type '({ title }: { title: string; }) => { payload: Todo; }' is not assignable to parameter of type '(payload?: { title: string; } | undefined, meta?: void | undefined) => { payload: Todo; }'.
Types of parameters '__0' and 'payload' are incompatible.
Type '{ title: string; } | undefined' is not assignable to type '{ title: string; }'.
Type 'undefined' is not assignable to type '{ title: string; }'.

from typesafe-actions.

What I want at 2) is to avoid dancing with payload type. Like this:

const someOtherAction = createStandardAction('somethingElse').map((payload: number) => ({
  meta: 'some meta info',
  payload,
}))

Don't sure if it possible

from typesafe-actions.

Ad 1) working fine here: https://github.com/piotrwitek/typesafe-actions-todo-app/blob/master/src/features/todos/actions.ts

Ad 2) map is for custom logic, better to use this in your case:

const increment = createStandardAction('INCREMENT')<void, MetaType>();
increment(undefined, 'meta info')

from typesafe-actions.

interface MetaType {
s: string;
}
const increment = createStandardAction('INCREMENT')<void, MetaType>();

gives me {type: 'INCREMENT'} without meta at all

from typesafe-actions.

Maybe problems with types in my case because of different settings in tsconfig.json
{
"compilerOptions": {
"jsx": "react",
"module": "commonjs",
"moduleResolution": "node",
"outDir": "ClientApp/dist/",
"sourceMap": true,
"strict": true,
"target": "es5",
"lib": [ "es6", "dom" ],
"noEmitOnError": true,
"baseUrl": "./",
"paths": {
...
}
},
"include": [ "ClientApp/**/*" ]
}

from typesafe-actions.

"strictFunctionTypes": false, removes some ts warnings/errors, but it's not a solution

from typesafe-actions.

"strictFunctionTypes": false, removes some ts warnings/errors, but it's not a solution

Ok this looks like something we have to investigate, thanks. #44

EDIT: From deeper analysis looks like use-case 2 issue is the symptom of strictFunctionTypes issue, so should be resolved with #44

from typesafe-actions.

Fix for use-case 1 issue tracked here: #47

from typesafe-actions.