Comparing version 2.5.2 to 2.6.2
@@ -75,3 +75,4 @@ "use strict"; | ||
error = result.error, | ||
data = result.data; | ||
data = result.data, | ||
isNonCritical = result.noncritical; | ||
sequencedData = _objectSpread(_defineProperty({}, prevKey, data), sequencedData); | ||
@@ -94,3 +95,3 @@ var promise = prevPromise.then(function (prevData) { | ||
}; | ||
} else if (error) { | ||
} else if (error && isNonCritical !== true) { | ||
return { | ||
@@ -97,0 +98,0 @@ status: 'complete', |
{ | ||
"name": "iguazu", | ||
"version": "2.5.2", | ||
"version": "2.6.2", | ||
"description": "An asynchronous data flow solution for React/Redux applications", | ||
@@ -5,0 +5,0 @@ "author": "Maia Teegarden", |
@@ -306,2 +306,15 @@ # Iguazu | ||
Function handlers require the previous calls to succeed to continue to the next by default. In the | ||
event a request returns with an error all remaining calls are flagged with the same error. To bypass | ||
this default behavior, you can wrap the function handler in `noncritical` to continue without the | ||
previous results. | ||
```javascript | ||
const sequenceLoadFunctions = sequence([ | ||
{ key: 'first', handler: () => dispatch(loadFirst()) }, | ||
{ key: 'second', handler: ({ first }) => dispatch(loadSecond(first.someParam)) }, | ||
{ key: 'unrelated', handler: noncritical(() => dispatch(loadUnrelated())) }, | ||
]); | ||
```` | ||
### Updating | ||
@@ -308,0 +321,0 @@ |
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
52783
544
487
0