Consolidating tags
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Right now, we treat namespace/name:tag as completely different projects.
What if we consolidate all name:tag entries to name, and from the project level, we retrieve the desired tag of the project?
e.g.
This 2 project in namespace page would be just ONE project.
Also, if user doesn't know tag of the project, then user can access project, even if there is only one existing tag.
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
No files, tests, or entry points are named. Start by tracing the namespace project-listing and project-access flows described in the issue, then define how tagged entries are represented and retrieved; done means one project is shown per name while users can select a tag or access the sole existing tag without knowing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100