Update Hashdiff Constant

[jfelchner]

Why This Change Is Necessary

The hashdiff gem is changing its constant and thus we need to do the
same.

How These Changes Address the Issue

Update HashDiff references to Hashdiff.

Side Effects Caused By This Change

This will not remove the hashdiff warning error until hashdiff's
1.0 version is released, at which point a bundle update will remove
the warning.

---

Actions:

• References hashdiff Uses Non-Standard Constant #822

[bblimke]

@jfelchner thank you. we can sync releases or the code can try to load Hashdiff constant and fallback to HashDiff is not present.

[jfelchner]

@bblimke no problem! hashdiff 0.4.0 was just released and the PR should be safe to merge now.

[jfelchner]

Once 0.4.0 is in the wild for a couple months, and your users have a chance to upgrade to latest, we'll release 1.0.

[jfelchner]

@bblimke because of webmock's popularity and the fact that the prior versions aren't pessimistically locked to hashdiff, we may want to make these same changes on the 1.x and 2.x branches and release new versions for them as well.

There are some popular gems that are locked to the 1.x and 2.x versions.

[teeparham]

If you re-run the travis build, it should work, now that 0.4.0 is released.

[jfelchner]

@teeparham Yep. At this point I'm just waiting for a reply from @bblimke

[jodosha]

@jfelchner Thanks for fixing this annoying warning. 👍

[jfelchner]

@bblimke can we get this merged?

[jfelchner]

@jodosha strictly speaking, this won't remove the warning just yet. But it will as soon as we release hashdiff 1.0 and you bundle update.

[jfelchner]

@bblimke do you want me to create patches for v1 and v2 as well?

[bblimke]

@jfelchner not sure it's worth supporting these old releases. people can always set versions of hashdiff in their Gemfiles. Though feel free to prepare these. I can release them as well.

I'll try to cut a new 3.x release tonight.

[jfelchner]

@bblimke not a problem. Up to you. I just wanted to offer. :)

[ndbroadbent]

For anyone else who wants to upgrade and remove the warning:

I upgraded to webmock version 3.6.0, which includes this change (renames the constant from HashDiff to Hashdiff). I also followed these instructions to upgrade to the hashdiff 1.0 beta:

gem 'hashdiff', ['>= 1.0.0.beta1', '< 2.0.0']

Then run bundle update hashdiff. This makes sure you are using the latest versions and will get rid of the warning.