Persisted document custom hash function #9996
Merged
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.
Description
This features allows for customization of the
hashAlgorithm
configuration for persisted documents in the client preset. This mitigates the need to support additional future algorithms beyondsha1
andsha256
and gives developers full flexibility for generating document hashes, unlocking new use-cases.Related #9994
Type of change
How Has This Been Tested?
Added three new test cases to
client-preset.spec.ts
. Ranyarn test client-preset
.custom hash remove whitespace
- This test case demonstrates basic functionality in a human-readable manner. Since the output is just the operation without whitespace, it's easy to tell if the custom hash function is broken.custom hash sha256
- This test case replicates the existing test casehashAlgorithm="sha256"
to ensure identical results.custom hash docs sha512
- This test case demonstrates a realistic, real-world use-case and was chosen as the example for the docs.Test Environment:
@graphql-codegen/...
:Checklist: