[AddLines] Fix update process to send changes to RecipeUpdate vs make them immediately #988
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.
Hi!
This was an oversight when I create
AddLinesConfigurator
.During
recipes:update
, the purpose of theupdate()
method in each configurator is to record what the "original" contents of a file would look like from the original recipe & what the "new" contents of a file would look like with the new recipe. Then, LATER, the patcher system creates a diff from these.The
AddLinesConfigurator
was going rogue and updating the files immediately, which caused the "patcher" system later to explode because this file was unexpectedly already modified.The changes are less drastic than they look, as code needed to be moved from some public methods -> private methods.
Cheers!