chore: follow up after introducing truncate method #80
+7
−5
Conversation
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
oleg-jukovec
requested changes
Aug 1, 2025
palage4a
force-pushed
the
palage4a/truncate-followup
branch
from
b8843f0 to
27702fd
Compare
Pull Request Test Coverage Report for Build 16777782542Details
💛 - Coveralls |
oleg-jukovec
approved these changes
Aug 6, 2025
palage4a
force-pushed
the
palage4a/truncate-followup
branch
from
27702fd to
c0bd390
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.
This PR contains changes which completing introducing of truncate() method.
Here added changelog entry, mention of new method in metrics description. Also fixes minor formatting issue.
Follow-up for #78