Release blog 4.7 #1210
Merged
Release blog 4.7 #1210
Conversation
This file contains 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
✅ Deploy Preview for ember-blog ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
runspired
approved these changes
Sep 12, 2022
content/ember-released-4-7.md
Outdated
|
|
||
| Today the Ember project is releasing version 4.7 of Ember.js, Ember Data, and Ember CLI. | ||
|
|
||
| This release kicks off the 4.7 beta cycle for all sub-projects. We encourage our community (especially addon authors) to help test these beta builds and report any bugs before they are published as a final release in six weeks' time. The [ember-try](https://github.com/ember-cli/ember-try) addon is a great way to continuously test your projects against the latest Ember releases. |
There was a problem hiding this comment.
Suggested change
| This release kicks off the 4.7 beta cycle for all sub-projects. We encourage our community (especially addon authors) to help test these beta builds and report any bugs before they are published as a final release in six weeks' time. The [ember-try](https://github.com/ember-cli/ember-try) addon is a great way to continuously test your projects against the latest Ember releases. | |
| This release kicks off the 4.8 beta cycle for all sub-projects. We encourage our community (especially addon authors) to help test these beta builds and report any bugs before they are published as a final release in six weeks' time. The [ember-try](https://github.com/ember-cli/ember-try) addon is a great way to continuously test your projects against the latest Ember releases. |
content/ember-released-4-7.md
Outdated
| - [#8084](https://github.com/emberjs/data/pull/8084) Eliminate InternalModel, nearly all private API's have undergone significant change, if your app previously used these APIs the most likely refactor is to use a custom model or a custom cache. | ||
| - [#8115](https://github.com/emberjs/data/pull/8115) Implement strict relationships ([RFC 739](https://rfcs.emberjs.com/id/0739-ember-data-deprecate-non-strict-relationships)). | ||
|
|
||
| Support for the `toJSON` method on Ember Data records has been removed. It was deprecated in `3.x` and slated for removal in `4.x`. |
There was a problem hiding this comment.
this occurred a while back, and support was removed in 4.0, not sure how it is getting into this blog post
There was a problem hiding this comment.
This was automatically generated. I've removed it!
content/ember-released-4-7.md
Outdated
|
|
||
| #### Deprecations | ||
|
|
||
| Ember Data 4.7 introduced 8 deprecations. Additional details are in the [release notes](https://github.com/emberjs/data/releases/tag/v4.7.1). |
There was a problem hiding this comment.
while there are only 8 PRs implementing deprecations there are 13 total. They are:
- deprecate model.reopen emberjs/rfcs#738
- deprecate early static emberjs/rfcs#741
- deprecate importable helper functions emberjs/rfcs#742
- deprecate non-promise promise-many-array APIs emberjs/rfcs#745
- deprecate v1-cache store APIs emberjs/rfcs#461
- deprecate v1-cache emberjs/rfcs#461
- deprecate using
A()on RecordArray/ManyArray/PromiseManyArray emberjs/rfcs#846 - deprecate relationships without a specified type emberjs/rfcs#739
- deprecate relationships without specified async behavior emberjs/rfcs#739
- deprecate relationships without an explicit inverse emberjs/rfcs#739
- deprecate polymorphic relationships without explicit polymorphic flags emberjs/rfcs#793
- deprecate promise-array and promise-object return values emberjs/rfcs#846
- deprecate array-like APIs (non native array APIs) on array proxies emberjs/rfcs#846
There was a problem hiding this comment.
Cool I'll change it to 13 and people could find the docs in the release notes correct?
|
|
||
| ### Changes in Ember Data 4.7 | ||
|
|
||
| Version 4.7 implements a "2.1" cache spec while deprecating the v1 cache spec. This spec differs somewhat from the [original 2.0 RFC](https://rfcs.emberjs.com/id/0461-ember-data-singleton-record-data), an updated RFC specifying the modifications will be published soon. Users looking to migrate to the 2.1 cache should expect that the finalized version of 2.1 enforces that the cache is always a singleton (vs merely allowed to be a singleton), and that data provided to the store and queries to the store from the cache should always contain identifiers in their stable form. This latter point is enforced in 4.7, the former is not yet enforced. |
There was a problem hiding this comment.
The performance changes are the big callout to make, you can probably just directly copy that portion of the release notes: https://github.com/emberjs/data/releases/tag/v4.7.1
There was a problem hiding this comment.
Cool, will add that too
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release blogpost 4.7