Add averageDistanceThreshold Option for Stroke Matching Leniency #307
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
Codecov ReportPatch coverage:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #307 +/- ##
=======================================
Coverage 96.40% 96.41%
=======================================
Files 32 32
Lines 1141 1144 +3
Branches 209 212 +3
=======================================
+ Hits 1100 1103 +3
Misses 37 37
Partials 4 4
☔ View full report in Codecov by Sentry. |
|
Looks good! |
|
🎉 This PR is included in version 3.6.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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 pull request introduces an averageDistanceThreshold option to the strokeMatches function, allowing users to configure the leniency of stroke matching based on distance.
This change provides more flexibility for users who want to adjust the leniency of stroke matching, especially in scenarios where the direction of the stroke is more important than its exact position.