summaryrefslogtreecommitdiff
path: root/UPGRADING.md
diff options
context:
space:
mode:
authorBobby McDonald <BobbyMcWho@users.noreply.github.com>2019-10-14 14:14:47 -0400
committerDaniel Doubrovkine (dB.) @dblockdotorg <dblock@dblock.org>2019-10-14 14:14:47 -0400
commit1a30427c9db1bdf974530aeddf90b305a3a621a5 (patch)
tree7dde72202b0fbfdd250113aa119239c322bac107 /UPGRADING.md
parentca3604516b5725b30a290482c219ca55fca5de49 (diff)
downloadhashie-1a30427c9db1bdf974530aeddf90b305a3a621a5.tar.gz
Allow mash error silencing (#488)
Diffstat (limited to 'UPGRADING.md')
-rw-r--r--UPGRADING.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/UPGRADING.md b/UPGRADING.md
index ce01eca..1374e10 100644
--- a/UPGRADING.md
+++ b/UPGRADING.md
@@ -36,10 +36,14 @@ p cool_parents
This may make places where you had to re-make the Mash redundant, and may cause unintended side effects if your application was expecting a plain old ruby Hash.
-### Ruby 2.6: Mash#merge and Mash#merge!
+#### Ruby 2.6: Mash#merge and Mash#merge!
In Ruby > 2.6.0, Hashie now supports passing multiple hash and Mash objects to Mash#merge and Mash#merge!.
+#### Hashie::Mash::CannotDisableMashWarnings error class is removed
+
+There shouldn't really be a case that anyone was relying on catching this specific error, but if so, they should change it to rescue Hashie::Extensions::KeyConflictWarning::CannotDisableMashWarnings
+
### Upgrading to 3.7.0
#### Mash#load takes options