fix(target): render templates before comparing in status/diff/check#23
Merged
Conversation
ComputeChanges only compared raw source file hashes, so changing a variable in an include file produced no visible diff (the template source hadn't changed). Now it accepts an optional template context and encryptor, renders template/encrypted files before hashing, and compares the rendered hash against the target — matching what the apply path already did.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
ComputeChanges only compared raw source file hashes, so changing a
variable in an include file produced no visible diff (the template
source hadn't changed). Now it accepts an optional template context
and encryptor, renders template/encrypted files before hashing, and
compares the rendered hash against the target — matching what the
apply path already did.