Hashes in existing projects break with new Dhall version about spago HOT 2 CLOSED

@f-f: I think I just need to hurry up and standardize dhall-lang/dhall-lang#335. That seems like the correct solution to this

from spago.

@Gabriel439 would you have any suggestion on how to go about fixing this? The goal here is to migrate existing configs to the new version/hashes as automatically as possible.

I considered the following flow:

• if there's a hash and a cache hit, try to decodeWithVersion it. If it's an old version substitute the new current version of the standard in the Haskell-CBOR Term and try to decode anyways.
• If this last decoding is successful, refreeze the import with the current standard version

Would this makes sense?

I took a stab at a modified version of Dhall.Binary.decodeWithVersion, but Dhall.Binary.decode is not exported (and I'm not sure it'd be a good idea to export it?), so I'm unsure how to proceed

from spago.