Documentation inconsistency - error.true not set anymore from createAction
See original GitHub issueIn createAction with payload Errror documentation, it is mentionned that the action.error
will be set to true
.
const increment = createAction('INCREMENT');
const error = new TypeError('not a number');
expect(increment(error)).to.deep.equal({
type: 'INCREMENT',
payload: error,
error: true
});
This was the case but is not anymore (master)
It seems to have been lost somehow from this commit
Either the documentation has to be adapted or the feature restored.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Web service error codes (Microsoft Dataverse) - Power Apps
This topic lists the error codes you might encounter when you debug your code.
Read more >Poor Documentation: Why It Happens and How to Fix It
For physicians, documentation that impairs patient evaluation and/or treatment would receive poor marks. For a coder, "poor documentation would be defined as ...
Read more >TIBCO EBX® Documentation - 5.9.17
activation (in EBX® configuration file) must be true or false (case-insensitive). Any other value throws an fatal exception at server launch. Bug fixes....
Read more >Error Messages - Product Documentation Center
The file QueMgr.sid is not actually used anymore. You should set P3_MASTER and P3_PORT environment variables, or use the org.cfg file.
Read more >Enterprise Manager Ops Center Release Notes
1 Solaris 10 Global Zone Shows Kernel Zone Create Action to be Available. LUNs for Zone Storage Does Not Get Locked. Add Assets...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There is the problem. Our library is called redux-actions. You are using the wrong library 😉 Our latest version is
0.10.1
.It works much better with the proper one…
Thank you… it did seem strange the documentation was not in sync with the code.