[Customer Entity] Add POST /service-requests/search endpoint - #903
Conversation
|
Warning Review limit reached
More reviews will be available in 48 minutes and 51 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughAdds a ChangesSearch Service Requests endpoint
Sequence DiagramsequenceDiagram
participant Client
participant Router as routes.go
participant Handler as CaseHandler.SearchServiceRequests
participant snSvc as snCaseService.SearchServiceRequests
participant Choreo as POST /cases/search
Client->>Router: POST /service-requests/search
Router->>Handler: dispatch
Handler->>Handler: decode body into SearchServiceRequestsRequest
Handler->>snSvc: SearchServiceRequests(ctx, req)
snSvc->>snSvc: validate pagination, searchQuery, date ranges
snSvc->>snSvc: extract x-user-id-token from ctx
snSvc->>Choreo: POST /cases/search (caseTypes=["service_request"])
Choreo-->>snSvc: snServiceRequestsResponse
snSvc->>snSvc: map cases to []domain.ServiceRequestView
snSvc-->>Handler: SearchServiceRequestsResponse
Handler-->>Client: 200 application/json
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@entity-service/internal/domain/entity.go`:
- Line 637: The comment for SearchServiceRequestsRequest contains a typo in the
endpoint path. Update the comment from `POST /service-request/search` (singular)
to `POST /service-requests/search` (plural) to match the actual registered
route. Also locate and fix any matching handler comment that references this
endpoint with the same singular path typo to maintain consistency throughout the
codebase.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 4c1fde57-aa64-4e34-8c1d-5f066f8f0e99
📒 Files selected for processing (6)
entity-service/internal/domain/entity.goentity-service/internal/handler/case_handler.goentity-service/internal/server/routes.goentity-service/internal/service/case_service.goentity-service/internal/service/interfaces.goentity-service/internal/service/sn_case_service.go
…and add OpenAPI spec\
…case search filters - Add POST /service-requests/search endpoint (entity-service PR #903) - Extend CaseSearchFilters with date range (closed/created/updated), createdBy, and createdByMe fields (entity-service PR #902) - Update OpenAPI spec with new path, schemas, and filter fields - Extend entityCaseClient interface and update test mock Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Summary
POST /service-requests/searchendpoint (ServiceNow only) — proxies to SNPOST /cases/searchwithcaseTypes: ["service_request"]and returns a service-request-specific response shape including catalog, catalogItem, assignedTeam, workState, and conversation fieldsSummary by CodeRabbit