Materials-Consortia / Materials-Consortia/optimade-python-tools
Test "available_endpoints" in validator
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 91
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
The endpoints mentioned in data->attributes->available_endpoints should be called and tested, simply to see whether they return a 2xx response, failing otherwise.
This is a simple sanity check - the content shouldn't be investigated further.
The validator may also check that entry endpoints are correctly listed here if found by querying them directly.
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 by locating the validator entry point that processes data.attributes.available_endpoints and review how it currently handles endpoint validation. The work is done when listed endpoints are called and required to return 2xx responses, with entry endpoints also checked against the discovered listing where applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend-api-design, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100