Inconsistency on ETag calculation
jisantuc opened this issue · comments
Describe the bug
Sometimes we return a hash for the ETag from the validated item (which checks some extension properties). Other times we return a hash for the original JSON document.
Expected behavior
We should return hashes of the same thing everywhere.
Additional context
Haven't been bitten by this yet, but I can imagine a client getting annoyed by it.