Class <Interface> Adapter
public⚠️ This is LEGACY documentation for a feature that is no longer encouraged to be used. If starting a new app or thinking of implementing a new adapter, consider writing a Handler instead to be used with the RequestManager
The following documentation describes the methods an adapter should implement with descriptions around when an application might expect these methods to be called.
Methods that are not required are marked as optional.
coalesceFindRequests [OPTIONAL] public
Defined in ../ember-data-types/q/minimum-adapter-interface.ts:434
If your adapter implements findMany, setting this to true will cause findRecord
requests triggered within the same runloop to be coalesced into one or more calls
to adapter.findMany. The number of calls made and the records contained in each call
can be tuned by your adapter's groupRecordsForHasMany method.
Implementing coalescing using this flag and the associated methods does not always offer the right level of correctness, timing control or granularity. If your application would be better suited coalescing across multiple types, coalescing for longer than a single runloop, or with a more custom request structure, coalescing within your application adapter may prove more effective.