Invalid language argument in Translation service shows incorrect error
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 2
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
This should be pretty easy to fix by just adding a custom RPC type for the supported languages.
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 Translation service and its RPC definition, then inspect how the language argument is validated. Confirm the supported languages and verify that an invalid language produces the correct error message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100