Current Focus

Current Objective

Implement Secure User Registration & CRUD (Milestone 1).

Current Blocker

None.

Next Action !!!!

Implement profile retrieval (GET /users/me) and partial update (PATCH /users/me) endpoints.

Tactical actions for today's session:
1. Design the UserUpdate Pydantic schema in src/schemas/users.py (ensuring all fields are optional to support partial PATCH updates).
2. Implement the GET /users/me endpoint in src/routers/users.py to return a dummy user profile matching UserResponse.
3. Implement the PATCH /users/me endpoint in src/routers/users.py accepting the UserUpdate model and returning a merged dummy UserResponse.
4. Add automated tests in tests/test_users.py (or tests/test_auth.py) to verify validation and responses.

Step 1 — Read only what you need (30–60 min) --

DONE

Open the official Pydantic documentation and ignore everything except the pieces required to build request models.

Specifically answer these questions in your new guide:

• Why does Pydantic exist?
• What is BaseModel?
• How does automatic validation work?
• How does FastAPI use Pydantic?
• How do I declare fields?
• How do I validate common types (str, int, EmailStr, etc.)?
• How do validation errors look?

Step 2 — Build while reading

After every section, jump to BiteTrack.

For example:

Documentation:

class User(BaseModel):
    username: str

Immediately write

class UserRegister(BaseModel):
    ...

Even if it's incomplete.

Step 3 — Decide API contract

Before writing routes, answer questions like:

Request

{
    "email": "...",
    "password": "...",
    "full_name": "..."
}

Response

{
    "id": "...",
    "email": "...",
    "full_name": "..."
}

Notice something?

This is no longer a Pydantic problem: It's API design.

Step 4 — Implement a dummy endpoint

No database. No hashing. No SQLAlchemy.

Just:

@app.post(...)
def register(user: UserRegister):
    ...

Return fake data. Your goal is to watch FastAPI validate the request automatically.