Open skurgansky-sugarcrm opened 5 years ago
yeah. I use redux-actions latest version and i suppose they have conflict here.
btw why payload have to be object in createLogic config ? seems wrong
error
is only true or undefined, that's the standard
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/redux-actions/index.d.ts#L22 https://github.com/jeffbski/redux-logic/blob/master/definitions/action.d.ts#L43 https://github.com/jeffbski/redux-logic/blob/master/definitions/action.d.ts#L56
redux-logic have type conflict with redux-action
ping
redux-logic type more strict, like https://github.com/redux-utilities/flux-standard-action
redux-logic type doesn't say & { error?: true }
like its described in flux-standard-action (FSA)
The optional error property MAY be set to true if the action represents an error.
An action whose error is true is analogous to a rejected Promise. By convention, the payload SHOULD be an error object.
If error has any other value besides true, including undefined and null, the action MUST NOT be interpreted as an error.
It says & { error?: false }
why ?
current type definitions version
error:
i think it should be (StandardAction<Type, Payload, Meta> & { error?: boolean }); ?