Feature: proper full-text search
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 10
- Forks
- 0
- Avg merge
- 2h 52m
- Merged PRs (30d)
- 20
Description
Tier 4 — feature idea
Why
SearchAsync lowercases and calls Contains on four columns, which translates to LIKE '%term%' — no index, no ranking, no multi-word support, no stemming. It degrades badly past a few thousand rows and cannot rank a title match above a notes match.
Evidence
LearnStack.Core/Services/LearningResourceService.cs:139-153
Sketch
SQL Server full-text index over Title, Description, Notes and Tags, queried with CONTAINSTABLE for ranking; fall back to LIKE in the SQLite test environment.
Notes
Should land together with the pagination work — they touch the same query path.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with SearchAsync in LearnStack.Core/Services/LearningResourceService.cs:139-153 and inspect the existing query path alongside the planned pagination work. Check the SQL Server full-text and SQLite test-environment constraints; done means multi-word search supports ranking across Title, Description, Notes, and Tags while retaining the SQLite fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql, sqlite
- Domain
- backend, databases, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100