Validate configuration in endpoint
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 161
- Forks
- 141
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 138
Description
During startup we already validate the configuration to allow feedback to the user.
We would also need to validate the configuration sent to the server endpoint to determine if the simulation could start or not.
Warnings should be omitted, as they would already have been exposed to the user.
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 tracing the existing startup configuration validation and the server endpoint that receives configuration. Determine how validation results are handled at the endpoint; done means invalid configurations prevent the simulation from starting while warnings are omitted because they were already shown to the user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100