Add a sha256 hash over the OCA Bundles file to the generated JSON lists of bundles #106
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses #82 by adding a sha256 hash over the OCA Bundle to the JSON lists of bundles. A client can load the list and check the hash against a saved value to determine if the OCA Bundles needs to be reloaded.
@wadeking98 -- still a bit nervous this will break production. Could you run a local test of the current released BC Wallet code using my branch (https://github.com/swcurran/aries-oca-bundles/tree/add-sha256-hash) that I'm trying to merge to make sure that the updated JSON file with the
sha256
field added doesn't break anything in the released BC Wallet people are using?If you are confident -- feel free to approve :-)