Releases: jklmli/monapt
Releases · jklmli/monapt
v2.1.0
v2.0.0
<a name"2.0.0">
2.0.0 (2018-03-17)
Features
Breaking Changes
Futures internally represent promises using native ES6
promises instead of when.js.
To migrate code which previously depended on when.js promises, wrap the
new native promise return values with a when
call:
Before: Future.create(42).promise
After: when(Future.create(42).promise)
Alternatively, you can choose to use a different promise library such as
Bluebird, or stick with native promises.
(7c0814c3)
v1.0.5
v1.0.4
v1.0.3
v1.0.2
1.0.1
Fixes
- Hotfix for 1.0.0 npm release not including any usable code, due to not building before releasing. The build step has now been added to CI, and CI will also automatically push to npm on a successful run thanks to semantic-release.
1.0.0
1.0.0 was a complete rewrite of Monapt - including everything from the implementation to the tooling to the tests. The result is almost the same API, but more true to the original Scala interface.
Breaking Changes
- All default exports have been removed to avoid ambiguity.
Future
now depends onwhen.Promise
, and uses it internally when representing promises.Future#onFailure
has been removed.Future#onSuccess
has been removed.Future#reject
has been removed.Monapt::flatten
has been renamed toOption::flatten
.Monapt::future
has been renamed toFuture::create
. It now accepts a
when.Promise<A> | when.Thenable<A> | A
.Option#reject
has been renamed toOption#filterNot
.Try#reject
has been removed.
These are all backed by type definitions, so compiling your code via TypeScript should reveal any
breakages.
0.7.1
Features
- support better type inferencing when using TypeScript 2's strict null checks.