Version 4.5 includes a number of new deprecations, a significant internal refactoring of the store architecture and several bug fixes.
Of note:
Users of just the core of EmberData may expect their builds to be 35-50% smaller. This is due to most of the legacy support for @ember-data/model having now found its final location at home in that package instead of within the @ember-data/store package. The size of @ember-data/store is reduced from ~16kb compressed to ~9.5kb compressed, potentially a little less depending on what deprecations are resolved and what other packages are present. We expect the core to continue to shrink as we complete the final stages of removing InternalModel, complete implementations for recently accepted deprecation RFCs, and introduce RecordDataV2.
Users of private store APIs may find these APIs have now been deprecated or removed. Internal restructuring will be high the next 6 months as we polish off the removal of InternalModel and continue to simplify codepaths which that removal allows us to do. All but a very few private methods have been entirely eliminated from the store.
New Deprecations target 5.0 and include:
deprecating some internal usage of RSVP.Promise that applications may have become dependent on if their tests are leaky
deprecating the type property on snapshots (which would lookup the model class).
deprecating store.find, a private method that has been maintained in case users accidentally fell into using ember's hidden autofetch behavior in routes
deprecating store.hasRecordForId, as peekRecord is generally more useful and provides the same information (and more).
deprecating store.recordWasInvalid, an unused internal api that ember-model-validations appears to be using.
deprecating passing strings to the schema lookup functions attributesDefinitionFor and relationshipsDefinitionFor, these APIs now expect an object with at least a type property representing the model name.
deprecating the -json-api fallback adapter, a hidden behavior that provided an adapter if the application failed to define one.
As always deprecated code can be eliminated from the build output by specifying the compatWith arg on the emberData configuration in your app.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps ember-data from 3.27.0 to 4.6.3.
Release notes
Sourced from ember-data's releases.
... (truncated)
Changelog
Sourced from ember-data's changelog.
... (truncated)
Commits
3223553
v4.6.374b4f79
add changelog for 4.6.31229195
allow ManyArray to work (for now)06f3fc3
v4.6.2a606054
add changelog for 4.6.23f7a861
fix: uuid polyfill logic (#8169)f1ff812
update for releasef723f5c
add more perf tests46db9e5
Clear subscriptions once unsubscribed, don't unnecessarily churn on subscript...536058d
updated perf testsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)