Fix parse issue with consecutive dates #77
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.
Closes #58
The issue was with the offset used for
extra_chars_to_be_added
. The inserted string is 12 characters long, but the code incremented the offset by only 10 - it should have been 11 (we're replacing 1 char with 12 chars, 12 - 1 = 11).Why wasn't it a problem? The
output
variable holds the json with extra spaces added, so it had some space to "correct" itself.There's a green pipeline using my other PR: https://github.com/kiskoza/crack/actions/runs/7386253493