OpenSourceFellows / OpenSourceFellows/map_dashboard_hackathon

Endpoint to create Users

Open
#48 0 comments 0 reactions 0 assignees View on GitHub

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

🛠️ Issue template for CRUD endpoints


📋 Endpoints Required

  • POST /api/v1/users — Create a new resource

🗂️ Data Schema

Describe or paste the expected request/response shape below.

Request Body

{
  advocacyGroupId: number,
  username: string,
  email: string,
  password: string,
  firstName: string,
  lastname: string,
  active: boolean <optional, should default to false on record creation if it doesn't already>
}

✅ 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or route entry points are named in the issue. Start by locating existing user or CRUD endpoint patterns, then compare their validation, middleware, error responses, and tests with the supplied request shape. Done means the POST endpoint, required access rules, validation, consistent errors, and happy-path and failure tests are covered.

Written by the indexing model from the issue text.

Assessment

Domain
api, authentication, authorization, backend, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.