Skip to content
module@warp-drive/legacy @legacy

Interface LegacyModelStoreSetupOptions<T>

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

Setup options for a legacy store configured to use Model with linksMode enabled, meaning no legacy adapter/serializer request infrastructure is required.

Extends

  • _LegacyStoreSetupOptions<T>

Type Parameters

T

T extends Cache

Properties

legacyRequests?

ts
optional legacyRequests?: false;

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

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

If legacyRequests is true, linksMode must be false

Default

ts
false

linksMode

ts
linksMode: true;

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

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

If legacyRequests is true, linksMode must be false

Default

ts
false

modelFragments?

ts
optional modelFragments?: boolean;

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

Whether to include support for ModelFragments migrations.

Default

ts
false

Inherited from

ts
_LegacyStoreSetupOptions.modelFragments

schemas?

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

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

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

ts
_LegacyStoreSetupOptions.schemas

Released under the MIT License.