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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve range split function and add unit tests #553
base: @Skalakid/fix-emoji-formatting
Are you sure you want to change the base?
Improve range split function and add unit tests #553
Changes from 6 commits
6fa4db9
3e83307
8fe38f3
5383871
0d8327e
cea5128
b39723f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still don't understand why it's better to modify
markdownRanges
in-place rather than create a new list. Could you please explain what's the actual benefit from doing so?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I must admit I might have misunderstood you during our last conversation about this.
I don't really see any benefit. I rewrote the function to not modify ranges in place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of implementing a custom
testRange
function (which btw should be namedassertRangeStartEndType
or something along these lines), let's just implementMarkdownRange#equals
method and rewrite the assertions in the unit tests like:This way we get more readable logs (with expected and actual value) if test fails rather than some generic assertion error in utility method.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To ensure more readable logs I've added also simple implementation of
MarkdownRange#toString
method.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it sufficient to compare ranges only based on
start
?Is
splitRangesOnEmojis
deterministic?Do we really need to sort the ranges?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the tests I wrote - I think so but in generality no.
It is.
splitRangesOnEmojis
does not guarantee any order of ranges. I've added sort so that tests work for different implementation of the method.