Update dependency fluture to v11 #5
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=80&v=4){kind=small}
![codelingo[bot]](https://avatars.githubusercontent.com/in/14339?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^4.3.5->^11.0.0Release Notes
fluture-js/Fluture
v11.0.1Compare Source
Corrects an issue in the TypeScript typings for the
chainRejfunction.v11.0.0Compare Source
hookare no longer allowed to reject. When they do, an Error is raised, and the process should be treated as corrupt.debugModeandFuture.alt.v10.3.1Compare Source
v10.3.0Compare Source
✨ New Features
alt). As a result, theorfunction is now an alias ofalt.v10.2.0Compare Source
✨ New Features
stack traces appended to their
stackproperty, allowing users to tracethe origin of an exception across multiple ticks.
Future.debugMode: A function to turn async stack traces on or off.🚀 Improvements
v10.1.1Compare Source
v10.1.0Compare Source
✨ New Features
Future#pipe: A method for inclusion of regular functions in afluent method-chain.
🚀 Improvements
v10.0.0Compare Source
index.mjs.jstoindex.mjs.Future.ap,Future.map,Future.bimap,Future.chain, orFuture.alton non-Fantasy Land types.If you were using any of these functions from Fluture to treat JavaScript's
native types as Fantasy Land algebraic types, you should migrate those
call-sites to use the Ramda or Sanctuary exported dispatchers instead.
Future.finallyno longer runs the cleanup Future when it is cancelled.If you rely on this behaviour, I urge you to rewrite the relevant code with
Future.hook(even if you don't upgrade Fluture).✨ New features
and the esm loader.
Future.offunction now has an aliasresolve, which is exportedstatically as well as exposed as a property on the Future constructor.
🐛 Bug fixes and improvements
Fluture.finallyare gone now that the behaviour has been removed.v9.0.2Compare Source
v9.0.1Compare Source
v9.0.0Compare Source
fork.nevernow use ageneric instead.
hook, the cancellationsignal is no longer sent to the disposal Future.
conflicts with exported values.
✨ New features
forkCatch, which allows for exception recovery.v8.0.2Compare Source
v8.0.1Compare Source
v8.0.0Compare Source
This release updates sanctuary-type-classes, which contains a breaking change. This change will only affect you if you are using
Future.mapon other Functors, specifically, Objects.Future.map, inherited properties are no longer transformed.v7.2.2Compare Source
v7.2.1Compare Source
v7.2.0Compare Source
✨ New features
🐛 Bug fixes
v7.1.3Compare Source
v7.1.2Compare Source
v7.1.1Compare Source
v7.1.0Compare Source
✨ New features
altfunction to use withAlttypes such asConcurrentFuture.of,ap,map,altandzerofunctions toPar, making theConcurrentFuturetype Static Land -compliant.✨ Improvements
apandmapare now overloaded to work onConcurrentFutureinstances as well asFutureinstances.extractLeftandextractRightmethods.v7.0.1Compare Source
v7.0.0Compare Source
b3851feThechainRecnamed export has been removed in favor of regular recursion.✨ New features
v6.3.0Compare Source
✨ Improvements
Future.parallelhas been made stack-safe.Future.parallelnow guarantees execution order.🗒️ Note
6.3.xfutures will not be compatible with6.2.xFutures, so when upgrading, make sure to upgrade all producers of Future instances.To avoid having to do this with future releases, I recommend setting Fluture as a peerDependency if you are maintaining a library which exposes Future instances to its users.
🐛 Bug fixes since
6.2.6Future.bothwas being executed twice under some circumstances.Future.parallelwithFuture.hookin a certain way led tofork()throwing an exception.v6.2.8Compare Source
v6.2.7Compare Source
v6.2.6Compare Source
✨ New features
Future.done()andFuture#done(): an easy way to fork using a Nodeback.🐛 Bug fixes and improvements
e24fa0fA problem related to the order in which asynchronous actions were executed was resolvede24fa0fParallel actions are now cancelled appropriately as one early-terminates9296445Optimize when parallel actions are executed446a27fPrevent asynchronous concurrent actions from running twice9c5900bImprovechains interoperability of different compatible versions of Fluturef434193MakeFuture#both()cancel the other when the one rejects.v6.2.5Compare Source
v6.2.4Compare Source
v6.2.3Compare Source
v6.2.2Compare Source
v6.2.1Compare Source
v6.2.0Compare Source
v6.1.1Compare Source
v6.1.0Compare Source
v6.0.1Compare Source
fluture/es5tofluture.Future#hookmethod (but not the function) has been removed.Future#cachemethod (but not the function) has been removed.Object.create,Object.assignandArray.isArray.ap-method have been flipped back.andandorno longer run the two Futures in parallel.fromPromisehas been renamed toencaseP.1a636d5chainRecis no longer curried and direct use is now discouraged.✨ New features
chain, are now stack safe!isNever.tryP, the nullary version ofencaseP.🐛 Bug fixes and improvements
tryPorencasePno longer get caught (and silenced) by the Promise.
Future.hookno longer cancels the acquire Future after it has settled.Future.hooknow always cancels running Futures appropriately.attempt = try,go = do,lastly = finally.sensible error messages.
192c34bAdded fast failure toencaseandencaseP.v5.0.0Compare Source
Future.or()has been flippedFuture.isForkable()has been removedFuture.fromForkable()has been removedFuture.cast()has been removedS.is(Future, Future.of(1))now returnstruerather thanfalse✨ New features
🐛 Bug fixes and improvements
Futures from other versions of Fluture as valid FuturesFuture.finally()now runsfinallycomputation when cancelledRenovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!".🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot. View repository job log here.