Skip to content

docs: backend requests — milestones read path + phase field - #4

Open
tanthehack wants to merge 7 commits into
mainfrom
docs/backend-requests
Open

docs: backend requests — milestones read path + phase field#4
tanthehack wants to merge 7 commits into
mainfrom
docs/backend-requests

Conversation

@tanthehack

Copy link
Copy Markdown
Contributor

Adds docs/backend-requests.md — the frontend's asks for the backend, written against the live spec (v3.0.0):

  1. Milestones read path — milestones are currently write-only (no GET, not embedded in project responses). Requests a GET /api/projects/{id}/milestones and embedding milestones in the portal project response.
  2. phase field on Milestone — a nullable string so milestones can be grouped by phase.

Plus related gaps (project updates read path, portal invoices).

Follow-up to #3 — this commit landed just after that PR merged, so it wasn't captured there.

@vercel

vercel Bot commented Aug 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
clover-admin Ready Ready Preview Aug 20, 2026 12:10pm

Add §3 — GET /api/notifications contract for the new admin header bell:
the Notification model, the four derived types (overdue invoices, pending
revisions, deliverables awaiting review, milestones due) and their href
targets. Read state is client-side, so no mark-read endpoint is requested.
…reason, attachments, deliverable link, notifications
…approval, manual deliverable→revision promotion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant