jeff/nucleo
1
0
Fork 0
mirror of https://github.com/solaeus/nucleo.git synced 2024-12-22 09:57:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Deprioritize camel case

Browse Source 
This change avoids scoring camel case higher than other casing
This commit is contained in:
Pascal Kuthe 2023-08-03 00:28:46 +02:00
parent 6cc59600e2
commit 960441f3b2
No known key found for this signature in database
GPG Key ID: D715E8655AE166A6
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
matcher/src/score.rs
View File

@ -16,9 +16,15 @@ pub(crate) const PENALTY_GAP_EXTENSION: u16 = 1;
pub(crate) const BONUS_BOUNDARY: u16 = SCORE_MATCH / 2; pub(crate) const BONUS_BOUNDARY: u16 = SCORE_MATCH / 2;
// Edge-triggered bonus for matches in camelCase words. // Edge-triggered bonus for matches in camelCase words.
// Compared to word-boundary case, they don't accompany single-character gaps // Their value should be BONUS_BOUNDARY - PENALTY_GAP_EXTENSION = 7.
// (e.g. FooBar vs. foo-bar), so we deduct bonus point accordingly. // However, this priporitzes camel case over non-camel case.
pub(crate) const BONUS_CAMEL123: u16 = BONUS_BOUNDARY - PENALTY_GAP_EXTENSION; // In fzf/skim this is not a problem since they score off the max
// consecutive bounus. However, we don't do that (because its incorrect)
// so to avoids prioritzing camel we use a lower bonus. I think that's fine
// usually camel case is wekaer boundary than actual wourd boundaries anyway
// This also has the nice sideeffect of perfectly balancing out
// camel case, snake case and the consecutive version of the word
pub(crate) const BONUS_CAMEL123: u16 = BONUS_CONSECUTIVE;
// Minimum bonus point given to characters in consecutive chunks. // Minimum bonus point given to characters in consecutive chunks.
// Note that bonus points for consecutive matches shouldn't have needed if we // Note that bonus points for consecutive matches shouldn't have needed if we