This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Add String Matching Boost for Case Matches #9512
Closed
Closed
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
8de2c26
Add Case Boost to StringMatch
JeffryBooher 450a3cb
rethink priorities
JeffryBooher 18887e6
touch of cleanup
JeffryBooher 04280f3
fix rte with quick open
JeffryBooher f05a14b
fix quick open
JeffryBooher 9aef4bd
Merge branch 'master' into jeff/CodeHIntsCaseBoost
JeffryBooher 753d622
Merge branch 'master' into jeff/CodeHintsCaseBoost
JeffryBooher 094e40f
down to just S-R-U test
JeffryBooher 86b945a
add test for non-case match
JeffryBooher 1916493
all tests passing
JeffryBooher 4b53f48
name change and jsdoc updates
JeffryBooher d441044
update debug data
JeffryBooher 959140d
a few other name changes
JeffryBooher 60fc868
Merge branch 'master' into jeff/CodeHintsCaseBoost
JeffryBooher File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
Compute a value that is enough to trickle the non-case matches below the case-matches
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.
nit:
result.scoreDebug
should probably reflect this.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 added this below but I'm not 100% certain what should be debugged here. Do we think it's important to just show the beginning value computed due to case match or not or have debug show the
MAX_VALUE
and a deduction for case. Since it's just a really big number it seems that we don't get much distinction from showing how much was deduced so just having the beginning value was enough for me in my thinking but I wanted to get your opinion.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 was basically just thinking that
scoreDebug
should reflect the actual score, so you can get an idea of what you're looking at if you're trying to debug it.