qdrant / qdrant/demo-code-search
Nitpick: Possible improvements
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 62
- Forks
- 19
- Avg merge
- 9d 4h
- Merged PRs (30d)
- 1
Description
@kartik-gupta-ij This is really good.
Some suggestions from my side. Whether you implement them or not is up to you :)
- Add a link to the Qdrant repo. Highlight existing occurrences of "Qdrant" as a link with a visible colour and underline it.
- Add a small explanation of how it works, the model used, etc.
- Pressing the back button (on the keyboard) doesn't bring me back to the search page.
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 locating the search page and the existing occurrences of “Qdrant”; no files or tests are named in the issue. Done means the Qdrant link is visibly styled, the page explains how it works and which model is used, and the keyboard back button returns to the search page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100