Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Releases: immutable-js/immutable-js

v5.1.4

13 Oct 07:26

Choose a tag to compare

What's Changed

Documentation

Internal

  • chore: Sort all imports and activate eslint import rule by@jdeniau in#2119

New Contributors

Full Changelog:v5.1.3...v5.1.4

Contributors

  • @jdeniau
  • @borracciaBlu
  • @lyannel
  • @JayMeDotDot
jdeniau, borracciaBlu, and 2 other contributors
Assets2
Loading
docxml reacted with thumbs up emoji
1 person reacted

v5.1.3

11 Jun 21:48

Choose a tag to compare

What's Changed

TypeScript

  • fix: allow readonly map entry constructor by@septs in#2123

Documentation

There has been a huge amount of changes in the documentation, mainly migrate from an autogenerated documentation from .d.ts file, to a proper documentation in markdown.
The playground has been included on nearly all method examples.
We added a page about browser extensions too:https://immutable-js.com/browser-extension/

Internal

New Contributors

Full Changelog:v5.1.2...v5.1.3

Contributors

  • @jdeniau
  • @septs
jdeniau and septs
Loading
docxml and markduan reacted with thumbs up emoji
2 people reacted

v5.1.2

05 May 22:27

Choose a tag to compare

What's Changed

Tooling

Documentation

New Contributors

Full Changelog:v5.1.1...v5.1.2

Contributors

  • @jdeniau
  • @giggo1604
  • @dependabot
  • @mrazauskas
jdeniau, giggo1604, and 2 other contributors
Loading
docxml and airmanxtw reacted with thumbs up emojijokester reacted with hooray emoji
3 people reacted

v5.1.1

26 Mar 00:02

Choose a tag to compare

What's Changed

Fix issue in builded types files in 5.1.0 due to cpy-cli upgrade

Full Changelog:v5.1.0...v5.1.1

Loading
airmanxtw, docxml, and mazerty reacted with thumbs up emoji
3 people reacted

v5.1.0

25 Mar 19:46

Choose a tag to compare

What's Changed

Internal

  • Upgrade typescript and typescript-eslint#2046 by@jdeniau
  • Upgrade to rollup 4#2049 by@jdeniau
  • Start migrating codebase to TypeScript without any runtime change nor .d.ts change:
  • add exception for code that should not happen in updateIn#2074 by@jdeniau
  • Reformat Range.toString for readability#2075 by@Ustin.Vaskin

New Contributors

Full Changelog:v5.0.2...v5.1.0

Contributors

  • @alexvictoor
  • @mazerty
  • @ustinvaskin
alexvictoor, mazerty, and ustinvaskin
Loading
docxml and mazerty reacted with thumbs up emoji
2 people reacted

v5.0.3

19 Nov 14:47

Choose a tag to compare

What's Changed

  • Fix List.VNode.removeAfter() / removeBefore() issue on some particular case by@alexvictoor in#2030

New Contributors

Full Changelog:v5.0.2...v5.0.3

Contributors

  • @alexvictoor
alexvictoor
Loading

v5.0.2

08 Nov 00:14

Choose a tag to compare

Changed

  • Fix wrong path for esm module after fix in 5.0.1

Full Changelog:v5.0.1...v5.0.2

Loading
ErcinDedeoglu, andreylysenko, supnate, airmanxtw, and docxml reacted with thumbs up emojiErcinDedeoglu reacted with hooray emojiErcinDedeoglu reacted with rocket emoji
5 people reacted

v5.0.1

07 Nov 23:57

Choose a tag to compare

What's Changed

Fixes

Internal

Full Changelog:v5.0.0...v5.0.1

Contributors

  • @iambumblehead
  • @mrazauskas
iambumblehead and mrazauskas
Loading

v5.0.0

03 Nov 23:04

Choose a tag to compare

Breaking changes

To sum up, thebig change in 5.0 is a Typescript change related toMap that is typed closer to the JS object. This is a huge change for TS users, but do not impact the runtime behavior. (seeImprove TypeScript definition forMap for more details)

Other breaking changes are:

[BREAKING] Remove deprecated methods:

Released in 5.0.0-rc.1

  • Map.of('k', 'v'): useMap([ [ 'k', 'v' ] ]) orMap({ k: 'v' })
  • Collection.isIterable: useisIterable directly
  • Collection.isKeyed: useisKeyed directly
  • Collection.isIndexed: useisIndexed directly
  • Collection.isAssociative: useisAssociative directly
  • Collection.isOrdered: useisOrdered directly

[BREAKING]OrdererMap andOrderedSet hashCode implementation has been fixed

Released in 5.0.0-rc.1

Fix issue implementation ofhashCode forOrdererMap andOrderedSet where equal objects might not return the samehashCode.

Changed in#2005

[BREAKING] Range function needs at least two defined parameters

Released in 5.0.0-beta.5

Range withundefined would end in an infinite loop. Now, you need to define at least the start and end values.

If you need an infinite range, you can useRange(0, Infinity).

Changed in#1967 by@jdeniau

[Minor BC break] Remove default export

Released in 5.0.0-beta.1

Immutable does not export a default object containing all it's API anymore.
As a drawback, you can notimmport Immutable directly:

- import Immutable from 'immutable';+ import { List, Map } from 'immutable';- const l = Immutable.List([Immutable.Map({ a: 'A' })]);+ const l = List([Map({ a: 'A' })]);

If you want the non-recommanded, but shorter migration path, you can do this:

- import Immutable from 'immutable';+ import * as Immutable from 'immutable';  const l = Immutable.List([Immutable.Map({ a: 'A' })]);

[TypeScript Break] Improve TypeScript definition forMap

Released in 5.0.0-beta.1

If you do use TypeScript, then this change does not impact you : no runtime change here.
But if you use Map with TypeScript, this is a HUGE change !
Imagine the following code

constm=Map({length:3,1:'one'});

This was previously typed asMap<string, string | number>

and return type ofm.get('length') orm.get('inexistant') was typed asstring | number | undefined.

This madeMap really unusable with TypeScript.

Now the Map is typed like this:

MapOf<{length:number;1:string;}>

and the return type ofm.get('length') is typed asnumber.

The return ofm.get('inexistant') throw the TypeScript error:

Argument of type '"inexistant"' is not assignable to parameter of type '1 | "length"

If you want to keep the old definition

This is a minor BC for TS users, so if you want to keep the old definition, you can declare you Map like this:

constm=Map<string,string|number>({length:3,1:'one'});
If you need to type the Map with a larger definition

You might want to declare a wider definition, you can type your Map like this:

typeMyMapType={length:number;1:string|null;optionalProperty?:string;};constm=Map<MyMapType>({length:3,1:'one'});

Keep in mind that theMapOf will try to be consistant with the simple TypeScript object, so you can not do this:

Map({a:'a'}).set('b','b');Map({a:'a'}).delete('a');

Like a simple object, it will only work if the type is forced:

Map<{a:string;b?:string}>({a:'a'}).set('b','b');// b is forced in type and optionalMap<{a?:string}>({a:'a'}).delete('a');// you can only delete an optional key
Are allMap methods implemented ?

For now, onlyget,getIn,set,update,delete,remove,toJS,toJSON methods are implemented. All other methods will fallback to the basicMap definition. Other method definition will be added later, but as some might be really complex, we prefer the progressive enhancement on the most used functions.

Fixes

Internal

Full Changelog:v4.3.3...v5.0.0

Loading
bdurrer and andreylysenko reacted with hooray emojitotpero, nanot1m, bdurrer, and andreylysenko reacted with rocket emoji
4 people reacted

v5.0.0-rc.2

17 Oct 23:16

Choose a tag to compare

v5.0.0-rc.2Pre-release
Pre-release

What's Changed

Full Changelog:v5.0.0-beta.5...v5.0.0-rc.2

Contributors

  • @jdeniau
jdeniau
Loading
Heliodex, rodamaral, and totpero reacted with rocket emoji
3 people reacted
Previous134589
Previous

[8]ページ先頭

©2009-2025 Movatter.jp