OpenSourceFellows / OpenSourceFellows/map_dashboard_hackathon
Endpoint to update a DataSource
Open
Nobody has claimed this yet.
Advanced
California Tribal GIS Hackathon
- Dominant language
- HTML
- Stars
- 2
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
🛠️ Update DataSource
📋 Endpoints Required
-
PUT/api/v1/advocacy_groups/:id/data_sources/:id— Update resource
🗂️ Data Schema
Describe or paste the expected request/response shape below.
Any of:
{
name: string,
description: string,
url: string <optional>,
tags: string[],
allowAggregation: boolean
}
✅ Acceptance Criteria
- All endpoints return correct HTTP status codes
- Input validation is applied to request bodies and query params
- Errors return consistent, descriptive JSON responses
- Endpoints are protected by appropriate auth/authorization middleware
- Pagination supported on the list endpoint
- Unit tests cover each endpoint (happy path + error cases)
- Integration tests pass in CI
- OpenAPI / Swagger docs updated
🔒 Auth & Permissions
N/A
🔗 Related
💬 Additional Context
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 route and implementation for PUT /api/v1/advocacy_groups/:id/data_sources/:id. Review the listed DataSource fields and existing endpoint tests, then clarify the required authorization roles and OpenAPI documentation before making changes. Done means the update endpoint validates input, returns consistent statuses and errors, is protected appropriately, and has passing unit and integration tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100