csm-portal backend: time-card create + update passthrough - #990
Conversation
Add POST /time-cards (create) and PATCH /time-cards/{id} (update) BFF passthroughs
to the entity service, alongside the existing POST /time-cards/search. The PATCH
body carries either editable fields or a state transition ({"state":"approved"}
or {"state":"rejected","leadComment":"..."}); the entity service enforces
authorization. Entity client methods, handler interface + handlers, routes,
openapi paths/schemas, mock, and handler tests included.
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Parity with the entity-service contract (wso2-open-operations#989): reject an empty/no-op PATCH body in the spec; the entity service enforces it and this BFF passes the body through.
What
Adds BFF passthrough endpoints for time-card writes, alongside the existing
POST /time-cards/search:POST /time-cards— create.PATCH /time-cards/{id}— update. The body carries either editable fields, or a state transition:{"state":"approved"}or{"state":"rejected","leadComment":"..."}.Both are thin auth-checked passthroughs to the entity service (raw JSON body forwarded; UUID path param validated for the PATCH). Authorization is enforced downstream.
Layers
Entity client methods, handler interface + handlers, routes,
openapi.yaml(paths + schemas), test mock, and handler tests.go build,go testclean.Depends on
The entity-service time-card write endpoints (#989) — this BFF forwards to them.