Altnames support for /search/structured
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 259
- Forks
- 169
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 1
Description
Currently a single-line request for /v1/search?lang=es&text=Париж, Франция (Paris, France output in Spanish) handles altnames on the way in and out. However, the equivalent structured request handles neither.
Contributor guide
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 the /search/structured endpoint and compare its behavior with the linked /v1/search request for the Spanish Paris, France example. Done means structured requests handle alternate names on input and output consistently with the single-line request; the payload names no source files or tests, so those must be located first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100