ember-m3 - npm Package Versions
Changelog
0.7.6
- Fixed handling of model names normalization. The schema no longer needs to normalize when returning references, nested models and base model names.
Changelog
0.7.5
- Model supports client validation errors. For convenience with migrating from @ember-data/model,
errorsan instance of sameErrorsclass used by@ember-data/model, which provides list of vaidation errors.
Changelog
0.7.4
- bugfix:
setUnknownPropertyremove cache and child model data if value is not resolved.
Changelog
0.7.3
- bugfix:
setUnknownPropertyremove cache after setting a new value and only update cache when value is resolved.
Changelog
0.7.2
- bugfix:
setUnknownPropertyonly update cache when value is resolved.
Changelog
0.7.1
- bugfix: Now able to get
lengthofM3RecordArrayas property.
Changelog
0.7.0
-
breaking: Properties manually set, including those set in initial record creation, are treated as resolved. This means that
createRecord({ myprop })will not use transforms formyprop. -
bugfix: now able to set
RecordArrayproperties withRecordArrayvalues. Semantics are still update in-place, as when setting to arrays of models.
Changelog
0.6.0
-
breaking: To be consistent with the request types used in ember-data,
queryURLwill pass arequestTypeofqueryURL. Previouslyquery-urlwas passed. -
breaking: All arrays of references are now returned as
RecordArrays.schema.isAttributeArrayRefis therefore deprecated. -
store.queryURLwill now calladapter.queryURLif it exists, instead ofadapter.ajax. This is intended to be a hook for doing app-wide url conversion forstore.queryURLcalls beyond prepending the adapter namespace.
Changelog
0.5.1
- bugfix: when using
schemaInterfaceto compute attribute references from data other thankey, dependencies are now tracked andkeyis invalidated correctly when those dependencies are invalidated. (thanks @dnalagatla)
Changelog
0.5.0
- bugfix: prevent
notifyProperties(undefined)from nested models with no changed attributes (thanks @sangm) - nested models that specify type, id are not re-used when these change.
nullid is fine for indicating a uniform type that should always be reused when new properties come in (thanks @dnachev) - attribute semantics now merge (so missing attributes are not treated as deletes thanks @dnachev)