feat: add replacement field to Mutant #274
Merged
Conversation
This file contains 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
hugo-vrijswijk
force-pushed
the
replacement
branch
from
dbed971 to
e538f4b
Compare
hugo-vrijswijk
force-pushed
the
replacement
branch
2 times, most recently
from
36c3d25 to
62692a5
Compare
Adds a new field `replacement` to the Mutant class. This field contains the actually newly replaced part of the pattern, corresponding to the `location`. Reason for adding this is because there is a mismatch between `pattern` and `location`. So for accurate location reporting, we need the part of the `location` that has been changed.
hugo-vrijswijk
force-pushed
the
replacement
branch
from
62692a5 to
7e1cb80
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a new field
replacementto the Mutant class. This field contains the actually newly replaced part of the pattern, corresponding to thelocation.Reason for adding this is because there is a mismatch between
patternandlocation. So for accurate location reporting, we need the part of thelocationthat has been changed.This allows the report to look like this: