GIScience / GIScience/openpoiservice
Separate pois, list, stats to different paths
Open
- Dominant language
- Python
- Stars
- 199
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Instead of the parameter `request` I think it'd be more consistent to have path parameters instead.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the current API routes and the `request` parameter for the pois, list, and stats operations. Define the separate paths and verify that each operation is reachable without the existing parameter, since the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100