…confusion with String::hash. So removing the remove_method unbreaks bcrypt_hash again.
We've found too many issues with having metric_fu and its minions as our development dependency and it's easier to just drop them then to figure out how to fix it. If one wants to run code quality checks on the codebase it's obviously still possible but you need to handle deps installation on your own. What were the problems? 1) with metric_fu along with roodi etc in the gemfile bundling takes forever (ok, it takes about 40-60 minutes) 2) if we leave only metric_fu as the dep (which depends on roodi etc. anyway) we will get latest versions of the gems which unfortunatelly results with a weird error when running semipublic specs so we need to pin the versions which gets us back to the problem #1
Additionally common functionality of these properties has been exctracted into Flags module.
Otherwise specs are printing loads of deprecation warnings. It is related to property class lookup that won't work correctly if models are defined inside DataMapper::Types module (const_missing is not triggered).
value is a string. [#1335 state:resolved]