Orfel-HermesAI-Bot/MC-SurvivalWiki-Tips
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rollback: remove test tip #37 (was E2E test, will regenerate tomorrow)

Browse Source
This commit is contained in:
Hermes AI Bot
2026-07-17 17:49:14 +00:00
parent 9ccf8f275a
commit 8ae3dfea88
2 changed files with 2 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TIPS.md
+2
View File
@@ -25,3 +25,5 @@ Going forward, new tips are pushed automatically by the `mc_survival_tips.py` cr
- [Tip #32](tips/2026-07-13-032-performance-code-split-heavy-components-on-the-recipe-page.md) (2026-07-13) — **performance**: Code-split heavy components on the recipe page
- [Tip #34](tips/2026-07-15-034-social-user-comments-on-recipes.md) (2026-07-15) — **social**: User-Comments on recipes
- [Tip #37](tips/2026-07-17-037-search-fuzzy-search-for-items-recipes.md) (2026-07-17) — **search**: Fuzzy-Search for items & recipes
- **[ROLLBACK]** Tip #37 was generated as an E2E test on 2026-07-17; the tip itself is valid but was pushed during testing. It will be regenerated by tomorrow's cron run.
tips/2026-07-17-037-search-fuzzy-search-for-items-recipes.md
-20
View File
@@ -1,20 +0,0 @@
# Tip #37 — Fuzzy-Search for items & recipes
**Date:** 2026-07-17
**Category:** search
**Source:** MC-Survival Wiki Daily Tip (cron @ 18:00 MESZ)
## Fuzzy-Search for items & recipes
Fuzzy search lets the wiki match items and recipes even when a player misspells the name, for example 'diamnd sword' or 'nethrite' instead of the correct spelling. It solves the very common problem that players land on a recipe URL from Google or a friend's chat message and cannot type the canonical item name. Real-world server logs show that exact-match-only search produces a high bounce rate on the first query, and the fix is a Levenshtein or trigram fallback on top of the existing Prisma query. With a small alias table, this also doubles as a hand-curated 'what players actually call things' layer.
## Implementation tips
1. Add a server function in functions.ts that wraps Prisma queries with a Levenshtein or trigram fallback when no exact match is found.
2. Use fuse.js (lightweight, no deps issues) on the client for instant-as-you-type feedback before hitting the server.
3. Index item aliases (e.g. 'netherite scrap' ↔ 'ancient debris') in a small ItemAlias table — most leverage for least code.
4. Highlight matched characters in the result list so users see WHY a fuzzy hit scored.
## Watch out
- Fuzzy search is expensive — debounce input by 200ms and never run it on every keystroke without a limit.