json-molder v0.5.0

• #populate() now checks if the properties declared in the __children child model-description object are also present in the "parent" model-description and throws and Error if not.
• For the sake of sane code structure, a "computedProperty" now gets the full molder instance passed in addition to the ever present preparedOrigin object. A "computedProperty" is now able to use the powers of the processing molder instance.
• #extractNamespace() method is now public (renamed from _extractNamespace to extractNamespace as well as removed the @private tag from the documentation) in order to be called on a molder instance regulary.

json-molder v0.4.2

• #desolate() now throws an Error if a "computedProperty" (alias function) should be serialized as it seems impossible to code the opposite operation of the "computedProperty" dynamically.

json-molder v0.4.1

• Added necessary version bump to package.json to be able to npm publish the json-molder.

json-molder v0.4.0

• Did some heavy lifting on #desolate() so that it's stable enough to be used in production. It is now save to do the conversion (#populate()/#desolate()) from each end (JSON <--> Rich Model) via model-description.

json-molder v0.3.0

• Added the possibility to use properties containing a namespace within child model-description, supporting Object and Array child models. (Pull Request: 6b00868)

json-molder v0.2.0

Breaking Changes included in this version!

• "Reserved Words" are now marked with two underscores (see "namespace" (pre v0.2.0) vs "__namespace" (since v0.2.0)
• Every model-description can have any amount of child-model-descriptions under the "__children" property. Each child-model-description is a valid model-description itself which means that you can parse the model and its children recursively from any JSON resource.

json-molder 0.1.0

[DEV]: Pushed Version to 0.1.0

JSON-Molder 0.0.2

JSON-Molder 0.0.2 comes with the availability to not only form/populate "rich" models from a JSON Object via a "model-description" but to also reduce/desolate a "rich" model to a simpler representation.

This is achieved with the serializable Array of the "model-description", which is a great way to tell the model what properties should to be sent to the backend.