⚡ Optimize fuzzy clustering with Web Worker and fix logic #30
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Codacy's Analysis Summary0 new issue (≤ 0 issue) Review Pull Request in Codacy →
|
Optimized the fuzzy clustering feature in
NormalizationModalby moving the quadratic complexity calculation to a Web Worker (src/workers/clusteringWorker.ts). This prevents the UI from freezing during analysis of large datasets (e.g., 10k items).Additionally, corrected the clustering logic to accommodate
fuzzysortv3+, which returns positive scores (0..1) instead of negative scores. The previous negative thresholds were ineffective, potentially causing incorrect results. Implemented a dynamic positive threshold based on string length to maintain the original intent of "stricter matching for shorter strings".Benchmark: Processing 10k items takes ~6.5s (blocking main thread previously, now backgrounded). Correctness improved by stricter filtering.
PR created automatically by Jules for task 14630253936315555000 started by @lightmyfireadmin