OpenSourceFellows / OpenSourceFellows/map_dashboard_hackathon
Endpoint to update Users
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 Users
📋 Endpoints Required
-
PUT/api/v1/users/:id— Update resource
🗂️ Data Schema
Describe or paste the expected request/response shape below.
{
email: string,
username: string,
newPassword: string,
oldPassword: string <Required if newPassword is present, otherwise optional>,
firstName: string,
lastName: string,
active: 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
🔗 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 from the API route or controller for PUT /api/v1/users/:id and inspect the existing user endpoint patterns. Confirm request validation, status codes, JSON errors, and unit or integration test coverage against the listed schema; authentication middleware and OpenAPI documentation remain unspecified and unchecked.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100