summaryrefslogtreecommitdiff
path: root/UPGRADING.md
diff options
context:
space:
mode:
authordblock <dblock@dblock.org>2014-06-03 09:42:56 -0700
committerdblock <dblock@dblock.org>2014-06-03 09:42:56 -0700
commit4a059050df17a174d0583440e2fbf8aed7899c2a (patch)
tree4fd0c05a2a2524a69be66a005400a6283a9bfeb3 /UPGRADING.md
parentf54e9129d09671e77bdd6f7b42975fcee36ce278 (diff)
downloadhashie-4a059050df17a174d0583440e2fbf8aed7899c2a.tar.gz
Preparing for release, 3.0.v3.0.0
Diffstat (limited to 'UPGRADING.md')
-rw-r--r--UPGRADING.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/UPGRADING.md b/UPGRADING.md
index 8d9de59..611d307 100644
--- a/UPGRADING.md
+++ b/UPGRADING.md
@@ -5,11 +5,11 @@ Upgrading Hashie
#### Compatibility with Rails 4 Strong Parameters
-Version 2.1 introduced support to prevent default Rails 4 mass-assignment protection behavior. This was [issue #89](https://github.com/intridea/hashie/issues/89), resolved in [#104](https://github.com/intridea/hashie/pull/104). In version 2.2 this behavior has been removed in [#147](https://github.com/intridea/hashie/pull/147) in favor of a mixin and extracted into a separate gem in 3.0.
+Version 2.1 introduced support to prevent default Rails 4 mass-assignment protection behavior. This was [issue #89](https://github.com/intridea/hashie/issues/89), resolved in [#104](https://github.com/intridea/hashie/pull/104). In version 2.2 this behavior has been removed in [#147](https://github.com/intridea/hashie/pull/147) in favor of a mixin and finally extracted into a separate gem in Hashie 3.0.
-To enable 2.1 compatible behavior, use the ['hashie\_rails' gem](http://rubygems.org/gems/hashie_rails).
+To enable 2.1 compatible behavior with Rails 4, use the [hashie_rails](http://rubygems.org/gems/hashie_rails) gem.
-```bash
+```
gem 'hashie_rails'
```