Releases: emberjs/data
v5.1.2 | Now I've had time to think it over
Changelog (2023-08-17)
🐛 Bug Fix
- #8750 Backport into release (@jrjohnson)
- fix: @ember-data/debug should declare its peer-dependency on @ember-data/store #8703
- fix: de-dupe coalescing when includes or adapterOptions is present but still use findRecord #8704
- fix: make implicit relationship teardown following delete of related record safe #8705
- fix: catch errors during didCommit in DEBUG #8708
LTS - v4.4.2
LTS - v4.12.3 | Daydream, déjà vu
Changelog (2023-07-13)
🐛 Bug Fix
- #8708 fix: catch errors during didCommit in DEBUG (@runspired)
- #8704 fix: de-dupe coalescing when includes or adapterOptions is present but still use findRecord (@runspired)
- #8705 fix: make implicit relationship teardown following delete of related record safe (@runspired)
- #8703 fix: @ember-data/debug should declare its peer-dependency on @ember-data/store (@runspired)
Committers: 1
- Chris Thoburn (@runspired)
v5.1.1 - I know it was wrong, but never said I was sorry
Changelog (2023-07-07)
🐛 Bug Fix
- #8685 fix: unloadAll(void) should not destroy the notification manager (backports #8684) (@runspired)
Committers: 1
- Chris Thoburn (@runspired)
LTS - v4.12.2 | With our head above the clouds, fallin' stupid like we're kids
Changelog (2023-07-07)
🚀 Enhancement
- #8660 DX: Nicer backtracking errors (@runspired)
🐛 Bug Fix
- #8686 fix: unloadAll(void) should not destroy the notification manager (backports #8684) (@runspired)
Committers: 1
- Chris Thoburn (@runspired)
v5.1.0 - We went to Hell, but we never came back
Changelog (2023-06-29)
🐛 Bug Fix
- #8657 fix: ensure deprecation configs are threaded to each package (@runspired)
- #8649 fix: NotificationManager should only invoke resource/document callbacks owned by the originating store (@runspired)
Committers: 1
- Chris Thoburn (@runspired)
LTS - v4.12.1 | Somehow the bedsheets are dirty
Changelog (2023-06-29)
🐛 Bug Fix
- #8656 fix: NotificationManager should only invoke resource/document callbacks owned by the originating store (#8649) (@runspired)
- #8571 [backport / release] Fix: don't clear RecordArray if remaining record does not match the removed record (@esbanarango)
- #8636 fix: backports polymorphism and app-config propagation fixes (@runspired)
- #8618 Various Backported Fixes for 4.12 LTS (@runspired)
Committers: 2
- Chris Thoburn (@runspired)
- Esteban (@esbanarango)
v5.0.0 - Rose Colored Lenses
This release removes code deprecated during 4.x.
🎵 We could stay like this forever.
Changelog
🐛 Bug Fix
- #8621 fix: normalizeErrorResponse should be resilient to non-string details (@NullVoxPopuli)
- #8598 fix: docs generation should maintain a stable relative path (@runspired)
- #8566 Avoid unnecessary identity notification when record is saved (@robbytx)
- #8597 fix: dont share promise cache for all fields (@runspired)
- #8594 fix: restore Store extends EmberObject :( (@runspired)
- #8570 Fix: don't clear RecordArray if remaining record does not match the removed record (@esbanarango)
- #8555 fix: fix polymorphic assertions when deprecated code is removed, improve polymorphic dx (@runspired)
🚿 Deprecation Removal
- #8550 chore: remove 4.x deprecations (@runspired)
📝 Documentation
- #8601 docs: fix forgotten references to FetchManager (@runspired)
- #8598 fix: docs generation should maintain a stable relative path (@runspired)
Committers: 4
- Chris Thoburn (@runspired)
- Esteban (@esbanarango)
- Robby Morgan (@robbytx)
- @NullVoxPopuli
v4.12.0 - Can't Cache This!
It might be the last release of the cycle, but this release comes packed with goodies, so here we'll try to unpack a bit of what's changed.
A Big Step Towards Modern Javascript Build Tooling Support
First, while all addons are still shipping as v1-addons, they now look a lot like v2-addons. We're referring to this as "v1-lite". We pre-build them with rollup leaving only the most minimal babel step to be done when included in your app. Generally this should result in applications seeing improved build times and vastly improved embroider support.
There are still a few blocking issues in ember-auto-import and embroider before EmberData will be able to flip the switch and ship its packages as v2-addons, but that's what is left at this point: a switch to flip. Many thanks to @richgt for his efforts to help us on this journey.
Documentation
Numerous APIs associated with the Cache, Notifications, Identity Management, and Record Lifecycle have new or improved docs. All packages have had their package overviews updated (some extensively, a few just a bit -- for now), and all packages now have a detailed README.
Deprecation documentation is now written inline alongside the flags that may be used to control granular deprecation stripping. Deprecation documentation will also continue to be added to the deprecation guides, though as of yet the 4.x guides have not been added there (we'd love help with this!).
A major focus of the 5.x cycle will be on refining and polishing the documentation for Polaris. A Quest issue has been opened and we'd love your help!
@ember-data/request has its first Stable Release!
This package introduces the RequestManager, a package that can be used independently (but also comes bundled with ember-data) that re-envisions how data fetching is managed for both EmberData and applications more broadly.
You may want to peruse the RFC or head over and read its documentation
With this release, all existing request flows in EmberData utilize the RequestManager. While Adapters and Serializers will continue to work via the legacy-handler, these concepts are now entirely optional and users should expect that over the course of the 5.x series as the new request management story is further polished that these legacy concepts will be deprecated and removed from the recommended experience. They will, however, likely live on much longer since their implementation is now as an integration into the request-pipeline of the future and as such is something an application could choose to integrate and continue using.
The Notifications Service has Expanded Capabilities
In addition to subscribing to notifications for individual resources, the notification service now enables subscribing to resource added/removed events and Document added/removed events.
Promises are now Native Promises
EmberData now uses native promises for all promise APIs instead of RSVP Promises. This can have some unexpected timing affects, there's an overview here
The Cache 2.1 Spec is Implemented
What this means in effect is that store.request is now a much ... much more powerful API than store.query. Requests are capable of providing a cache-key or being cached by URL, with full lifecycle control and notification subscriptions. Documents are a first-class citizen of the Cache and EmberData more broadly, we are no longer just a resource-cache. For the full motivations and a discussion of all the various capabilities this unlocks we recommend reading the RFC
To go with this, the JSON:API cache previously provided by @ember-data/record-data is now upgraded to the 2.1 spec and available as the @ember-data/json-api package. While this cache does not yet implement the full suite of cache 2.1 APIs, support for all Cache 2.1 APIs has been added to the store.
Changelog
🚀 Enhancement
- #8547 feat: Future.abort, additional tests and minor fixes (@runspired)
- #8539 feat: Rich Documents (@runspired)
- #8544 feat: error documents (@runspired)
- #8471 feat: cache.peek() (@runspired)
- #8375 feat: Cache.put (@runspired)
- #8456 feat: rename cache.pushData to cache.upsert (@runspired)
- #8455 chore: rename Cache.sync to Cache.patch to mirror RFC (@runspired)
- #8542 feat: full-relationship definitions when scaffolding with blueprints (@runspired)
- #8531 feat: stable document identity (@runspired)
- #8518 feat: enable request cache without hydration, better error handling by Fetch Handler (@runspired)
- #8501 chore: update imports to support RFC tweaks (@runspired)
- #8487 feat: relationship fetching as legacy op (@runspired)
- #8484 feat: break saveRecord up into legacy operations (@runspired)
- #8472 feat: Store.request (@runspired)
- #8473 chore: remove ember-fetch weirdness (@runspired)
- #8468 feat: cache.peek and store.request (@runspired)
- #8458 feat: Store.cache and Store.createCache (@runspired)
- #8454 feat: public API to support cache insert/remove operations (@runspired)
- #8358 feat: Store.notifications (@runspired)
- #8353 feat: prebuilt v1 addons (@runspired)
- #8285 feat: @ember-data/store as v2-lite addon (@runspired)
- #8347 feat: don't extend EmberObject/Service for Store (@runspired)
- #8342 fix: assign preload data always (@runspired)
- #7668 feat: allow .load()ing sync relationships (@machty)
🐛 Bug Fix
- #8517 fix: ensure cache-handler works as expected (@runspired)
- #8511 updates to lifetimes service and CacheHandler install (@runspired)
- #8453 chore: fix ArrayLike.setObjects deprecation message (@runspired)
- #8435 fix: de-cycle ember-concurrency access of promise (@runspired)
- #8400 fix: deprecated record-array reject use callback (@mrloop)
- #8399 fix: deprecated record-array rejectBy use optional value if supplied (@mrloop)
- #8436 perf: fix: eliminate SSR/Test memory leak (@runspired)
- #8432 fix: ensure classic computed chains support (@runspired)
- #8410 fix: add better embroider test and fix embroider compat (@mkszepp)
- #8354 fix: improve error/deprecation messaging for inverse fields (@runspired)
- #8348 fix: don't use isEqual from @ember/utils for comparing cache values (@runspired)
- #8345 fix: give more meaningful error if id matches but is number instead of string (@runspired)
- #8344 fix: improve object stringify and verbiage for relationship identifier errors (@runspired)
- [#8338](#83...
v4.11.3 - Roads? Where We're Going ...
Fixes a memory leak in SSR/Tests and Infinite Recursion bug in develop when yielded/awaited in an ember-concurrency task.