ComputerScienceHouse / ComputerScienceHouse/conditional
Refactor / Standardize Endpoints
- Dominant language
- Python
- Stars
- 12
- Forks
- 39
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 1
Description
As a software developer, I would like to see proper implementation of endpoints and adherence to RESTful guidelines.
Ex.
`GET` /attendance/hm => List of users eligible for HM attendance.
`POST` /attendance/hm => Endpoint for posting HM attendance.
Basically, make our endpoints make some semblance of sense.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Flask endpoint definitions and reviewing the existing attendance routes, especially the GET and POST examples for /attendance/hm. Document the current inconsistencies before changing them; done means the endpoints follow a consistent RESTful structure and existing behavior remains covered by the available tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100