* Do not rely on dm-core to coerce Symbol into a String, because it's default behavior is extremely permissive, and will likely be tightened to only coerce specific types.
With this change, dm-validations is compatible with active_model's requirements regarding the #errors and the #valid? method. The remaining aspects of of active_model compatibility are handled inside the dm-active_model plugin.
* Added gaurd clauses to each auto-validation method cleans up the logic and removes some nested conditional code. * Always pass the base options into the validation methods so that :allow_nil => true is always in effect in auto-validations * Changed usage of Hash#has_key? to Hash#key? as a matter of personal preference, and consistency with dm-core * Renamed infer_numeric_validation_for method to the more correct infer_type_validation_for * Minor formatting changes
* Resource#loaded_properties was removed from the API during a refactoring of dm-core internals. It probably won't get exposed in a different form, since it is possible to determine which properties are loaded using other approaches. Plus the loaded/unloaded behavior is something that happens inside a Resource and probably should not be exposed to the outside world.
…eTree is not available
…eTree is not available
* Skip requiring rcov if the syntax is invalid
* dm-validations now skips over extra auto-validation when the value is nil to prevent redundant error messages from being raised
Now all specs will still run (rather than aborting on first failure), but the exit status of the command will reflect the overall success or failure.
* It is only necessary to return presence error messages when a value is nil, not that the length is wrong (because that's obvious), or that the format is wrong (also obvious), etc.
* Removed unecessary require statements from dm-rest-adapter and dm-sweatshop. * Minor code cleanup in dm-types Rakefile
* Removed usage of rubygems from each Rakefile. It is automatically included by the rake command, so including it in each Rakefile is redundant. * Updated the shared hoe task file to require hoe ~>2.3.3 * Fixed broken require line in ferret adapter
Removed a lot of the complexity in specifying require paths and which specs to run, relying on defaults and not assuming rubygems as much as is practical. It's still possible to either run 'rake spec' or run the 'spec' command on individual files. If you want to run specs for individual files, you will need to do something to the effect of: export RUBYOPT=-Ispec Also, when running from a typical dev setup (dm-core and dm-more are in the same folder), specs will pick up the local version of dm-core instead of the gem version. This also happens for dm-more plugin specs that depend on other dm-more plugins.
Also, avoid hoe deprecation warnings by using Hoe.spec instead of Hoe.new