This will make sure that all the gems require everything they need to be fully functional.
1) This is a workaround for current bundler which doesn't yet respect the order in which the gems have been declared in the Gemfile, when doing a Bundler.require 2) Actually I also think it's good style to require all the code that we need in order to perform a task. Even if most applications will always require dm-core before requiring any of its plugins, it still doesn't hurt to be explicit and to avoid possible bugs in the first place.
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.
* Calling the generated tag_list writer methods with a blank String will delete all the receiver's tags. * Thx to Max Hawkins for the meat of this patch. [#1006 state:resolved]
* tag_collection= and tag_collection accept and return strings respectively, this eases the adding/editing of tags with a text_field * Updated the README with tag_collection example * Improved coverage by removing dm-validations and testing the taggables method on Tag
* There is no need for this gem to have a dependency on dm-validations. The specs do test to see how this gem functions when dm-validations is present, but it does not mean the gem should explicitly require the validations gem. We want to minimize the coupling between each dm-more gem as much as possible.
* Added dm-validations * use validates_present instead of an if statment * updated spec