@ember-data/store 5.1.0-alpha.8 → 5.1.0-beta.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/addon/-private.js +5634 -1
- package/addon/-private.js.map +1 -1
- package/addon/index.js +1 -1
- package/addon/index.js.map +1 -1
- package/package.json +21 -20
- package/addon/store-service-fe7f006c.js +0 -5634
- package/addon/store-service-fe7f006c.js.map +0 -1
package/README.md
CHANGED
|
@@ -87,7 +87,7 @@ Now that we have a `cache` let's setup something to handle fetching and saving d
|
|
|
87
87
|
|
|
88
88
|
When *Ember***Data** needs to fetch or save data it will pass that request to your application's `RequestManager` for fulfillment. How this fulfillment occurs (in-memory, device storage, via single or multiple API requests, etc.) is then up to the registered request handlers.
|
|
89
89
|
|
|
90
|
-
To start, let's install the `
|
|
90
|
+
To start, let's install the `RequestManager` from `@ember-data/request` and the basic `Fetch` handler from ``@ember-data/request/fetch`.
|
|
91
91
|
|
|
92
92
|
> **Note** If your app uses `GraphQL`, `REST` or different conventions for `JSON:API` than your cache expects, other handlers may better fit your data. You can author your own handler by creating one that conforms to the [handler interface](https://github.com/emberjs/data/tree/main/packages/request#handling-requests).
|
|
93
93
|
|