You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
transforms now come from a public instead of private import location
setConfig may be required?
extending @ember-data/store instead of ember-data/store now requires full configuration
super in hooks in classes extending @ember-data/store no longer works
model._notifyProperties has been removed
MAYBEFIX
adapter.useFetch is assigned in a new way, resulting in the getter approach in app adapters not working. fields approach works e.g. useFetch = false.
isRelationship and isAttribute on field meta is no longer present. These were meant to be private and not part of the spec, but some apps may have discovered and made use of them.
relationship graph uses the passed in arrays from operations that update remote state for perf, this exposes them to accidental mutation later. We should consider freezing and/or slicing these arrays in debug as this is mostly an issue with tests using mirage.
This can result in Relationship state sometimes storing non-stable identifiers
TO FIX
deprecated registerSchema does not setup schema in a way that avoids the store attempting to call createSchemaService
getSchemaDefinitionService only checks for schemas registered with registerSchema
The text was updated successfully, but these errors were encountered:
WONTFIX
@ember-data/store
instead ofember-data/store
now requires full configuration@ember-data/store
no longer worksmodel._notifyProperties
has been removedMAYBEFIX
adapter.useFetch
is assigned in a new way, resulting in the getter approach in app adapters not working. fields approach works e.g.useFetch = false
.isRelationship
andisAttribute
on field meta is no longer present. These were meant to be private and not part of the spec, but some apps may have discovered and made use of them.TO FIX
registerSchema
does not setup schema in a way that avoids the store attempting to callcreateSchemaService
getSchemaDefinitionService
only checks for schemas registered withregisterSchema
The text was updated successfully, but these errors were encountered: