v0.18.2 (Ember 4)

This release is the same as 0.18.1, but is made to work with Ember 4.0.

Published on NPM as ember-data-storefront@ember4.

Applications using Ember 3.x should continue to use 0.18.1.

v0.18.1

🐛 Bugfixes

• #427 Serve data from shoebox if storefront.maxAge is not set @xg-wang

🏠 Internal

• Dependency upgrades
• Fix CI

v0.18.0

💥 Breaking changes

• #396 Storefront only works with Ember 3.12 and above.

🏠 Internal

• Dependency upgrades

v0.17.3

🚀 New Features / Enhancements

• #369 Configure when shoebox expires @st-h

🏠 Internal

• Dependency upgrades

v0.17.2

🐛 Bugfixes

• #290 Fix get-key bug @hypothete

🏠 Internal

• Dependency upgrades

v0.17.1

🐛 Bugfixes

• #150 fastboot-adapter fails when different domains are used: remove domain and protocol from shoebox key @st-h

🏠 Internal

• Dependency upgrades

v0.17.0

💥 Breaking changes

• #133 Remove babel plugin to rewrite async relationships to sync

  This is only for users who have forceSyncRelationships: 'rewrite' in their config/environment.js.

  The babel plugin that automatically rewrote async relationships to sync has been removed. If you're interested in enforcing sync relationships in your application then have a look at our eslint-plugin-ember-data-sync-relationships plugin.

  If you're currently relying on storefront to rewrite all of your relationships to sync then you should manually change all of your relationships to { async: false } before upgrading to 0.17.0.

🐛 Bugfixes

• #131 Fix warning message

🏠 Internal

• Dependency upgrades

v0.16.3

🐛 Bugfixes

• #82 No relationship assertion for includes

🏠 Internal

• Add dependabot
• Test against Ember Data canary
• Dependency upgrades

v0.16.2

🐛 Bug fixes

• #79 Don't use hasOwnProperty check for query options

v0.16.1

Fixed a bug where loadRecords would not track includes [#66]

loadRecords will now track the includes it was called with, which allows models that enter the store with loadRecords to work with assert-must-preload. See #66 for the bug report.

There's also the potential for this bug fix to change the behavior of your app. Since models loaded with loadRecords weren't aware of their includes, they would always block the first time a relationship was loaded.

Before this bugfix, this is how storefront behaved:

// Prior to the bugfix
let posts = this.store.loadRecords('post', { include: 'comments' });
posts.firstObject.hasLoaded('comments') // => false
posts.firstObject.load('comments') // => blocking promise until the data is loaded

With this release, the new behavior is:

// After the bugfix
let posts = this.store.loadRecords('post', { include: 'comments' });
posts.firstObject.hasLoaded('comments') // => true
posts.firstObject.load('comments') // => instantly resolving promise + background reload