POSYDON-code / POSYDON-code/POSYDON
Add better checks on assumed input types/values to all functions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 45
- Forks
- 37
- Avg merge
- 8d 20h
- Merged PRs (30d)
- 5
Description
We have a lot of functions, which work currently with assumptions either only written in the doc-strings or even nowhere mentioned. All this can produce unforeseen runtime errors at any parts of the code.
A more specific example in the case of None type objects is already given in issue #236 .
Another common case are floats or integers to be of the correct type or range.
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 reviewing issue #236 and the project's Python functions and docstrings to identify assumptions about None values, integer or float types, and valid ranges. Define the scope of checks before changing code; done means the affected functions reject invalid inputs consistently and the relevant runtime-error cases are covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100