lambdaclass / lambdaclass/lambda_ethereum_consensus
[Validator API] Handle bad requests
Open
Nobody has claimed this yet.
Validator API
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
We should gracefully handle bad requests.
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
No files, tests, or entry points are named. Start by locating the Validator API request-handling entry points and identify which bad requests need graceful handling. Done means the expected behavior for invalid requests is defined and verified, but the issue does not specify those cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100