Feature: first-class categories and tags
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
Tags are a single comma-separated string on the resource today. There is no tag entity, so there is no autocomplete, no rename, no merge, no "all resources with this tag", and filtering is a LIKE '%tag%' scan that also matches substrings of unrelated tags.
Related: #2 (Categories for the resources).
Evidence
LearnStack.Core/Data/Models/LearningResource.cs:36—string? TagsLearnStack.Core/Services/LearningResourceService.cs:141-152—Tags.ToLower().Contains(term)
Sketch
Tag entity + ResourceTag join table, migration splitting existing strings, autocomplete in ResourceForm, tag chips as filters, tag rename/merge in settings.
Notes
Worth doing before the library grows — the data migration gets harder with volume.
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 by reading LearnStack.Core/Data/Models/LearningResource.cs:36 and LearnStack.Core/Services/LearningResourceService.cs:141-152, then trace ResourceForm and the existing migration setup. Check how current tag strings are stored, searched, and rendered before assessing the entity, join-table, migration, autocomplete, filter, and settings scope. Done means existing tags migrate without loss and the new search, editing, filtering, rename, and merge flows are verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, html
- Domain
- database, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100