module@warp-drive/legacy @legacy

Interface LegacyModelAndNetworkStoreSetupOptions<T extends Cache>

interface LegacyModelAndNetworkStoreSetupOptions<T extends Cache> extends _LegacyStoreSetupOptions<T> {
  legacyRequests?: false;
  linksMode: false;
  modelFragments?: boolean;
  schemas?: (
  | ResourceSchema
  | ObjectSchema)[];
}

Defined in: warp-drive-packages/legacy/src/index.ts:105

Setup options for a legacy store configured to use Model along with the legacy adapter/serializer network layer, but without the deprecated store.findRecord/findAll/query/etc. request methods.

Extends

• _LegacyStoreSetupOptions<T>

Type Parameters

T

T extends Cache

Properties

legacyRequests?

legacyRequests?: false;

Defined in: warp-drive-packages/legacy/src/index.ts:121

if true, all legacy request methods and supporting infrastructure will be available on the store.

If legacyRequests is true, linksMode must be false

Default

false

---

linksMode

linksMode: false;

Defined in: warp-drive-packages/legacy/src/index.ts:112

If true, it is presumed that no requests require use of the LegacyNetworkHandler and associated adapters/serializer methods.

Default

false

---

modelFragments?

modelFragments?: boolean;

Defined in: warp-drive-packages/legacy/src/index.ts:64

Whether to include support for ModelFragments migrations.

Default

false

Inherited from

_LegacyStoreSetupOptions.modelFragments

---

schemas?

schemas?: (
  | ResourceSchema
  | ObjectSchema)[];

Defined in: warp-drive-packages/legacy/src/index.ts:57

The ResourceSchemas or ObjectSchemas of entities migrated to no longer use Model.

CAUTION

Model is still able to be used directly as a source of schema when using useLegacyStore, however, its reliance on EmberObject, classic computeds and resolver behaviors mean that Model will stop working when these things are deprecated in Ember.

Inherited from

_LegacyStoreSetupOptions.schemas