Return the raw object data when running on Node v0.11.14+
That way all `inspect` options are always preserved.
When running on older version:
- Honour the depth argument passed to the custom `inspect` function.
- Disable color output, becase there is now way how to detect whether
colors were enabled or disabled by the top-level caller.
When building a list of errors for `ValidationError.message`, include
the values of invalid properties too.
In order to keep the message reasonably short, the values are truncated
at approx 32 characters.
2.13.0
* added test for sorting undefined values (Christian Vette)
* Fix the floating number comparison (Raymond Feng)
* Fix bad CLA URL in CONTRIBUTING.md (Ryan Graham)
* replace deprecated function __defineGetter__ (bitmage)
* add a flag to callback of findOrCreate to indicate find or create (Clark Wang)
* fix sorting of undefined values with multiple columns (Christian Vette)
* code style (cvette)
* fix sorting with undefined in memory connector (cvette)
* Added support for inline parameters like: new GeoPoint(-34, 150) (Simo Moujami)
* fix default include in default scope fails findById (Clark Wang)
* Added test for toString() (Simo Moujami)
* Additional formatting (Simo Moujami)
* Fixed constructor parameters and added bdd tests for constructor validation (Simo Moujami)
* Fixed indentation (Simo Moujami)
* Added mocha tests for GeoPoint (Simo Moujami)
* renamed intermediary variable (Simo Moujami)
* Fixed the haversine formula to calculate distance between 2 points properly (Simo Moujami)
2.12.0
* Relax the id comparison (Raymond Feng)
* Allow more flavors of nullable values from DB discovery (Raymond Feng)
* Fix a typo (Raymond Feng)
* docs.json: add lib/model.js (Miroslav Bajtoš)
* Update README.md (Rand McKinney)
* fix embedsOne error when embed instance is undefined or null (Clark Wang)
* Be explicit: set RelationDefinition multiple flag (Fabien Franzen)
* Allow hasOne relation to have a scope option (Clark Wang)
* fix skipping async validator will always fail if condition is un-fulfilled (Clark Wang)
If the validator configured with `{async:true}` option and `if/unless`
condition, validator should be skipped when the condition is un-fulfilled,
so the validator should be pass.
But currently, when skipping the validator, it calls `done(true)` which
accepts a `fail` flag as a param, this will fail the entire validation.
Signed-off-by: Clark Wang <clark.wangs@gmail.com>