9a9398b386
Adds Skooma-based OpenAPI validation so SDK-facing request specs can assert that documented request and response contracts match real Rails behavior. This also upgrades the spec to OpenAPI 3.1 and fixes contract drift uncovered while validating core application and platform resources. Closes None Why We want CI to catch OpenAPI drift before it reaches SDK consumers. While wiring validation in, this PR surfaced several mismatches between the documented contract and what the Rails endpoints actually accept or return. What this change does - Adds Skooma-backed OpenAPI validation to the request spec flow and a dedicated OpenAPI validation spec. - Migrates nullable schema definitions to OpenAPI 3.1-compatible unions. - Updates core SDK-facing schemas and payloads across accounts, contacts, conversations, inboxes, messages, teams, reporting events, and platform account resources. - Documents concrete runtime cases that were previously missing or inaccurate, including nested `profile` update payloads, multipart avatar uploads, required profile update bodies, nullable inbox feature flags, and message sender types that include both `Captain::Assistant` and senderless activity-style messages. - Regenerates the committed Swagger JSON and tag-group artifacts used by CI sync checks. Validation - `bundle exec rake swagger:build` - `bundle exec rspec spec/swagger/openapi_spec.rb` --------- Co-authored-by: Sojan Jose <sojan@pepalo.com>
43 lines
1.3 KiB
YAML
43 lines
1.3 KiB
YAML
type: array
|
|
description: Team summary report containing conversation statistics grouped by team.
|
|
items:
|
|
type: object
|
|
properties:
|
|
id:
|
|
type: number
|
|
description: The team ID
|
|
conversations_count:
|
|
type: number
|
|
description: Number of conversations assigned to the team during the date range
|
|
resolved_conversations_count:
|
|
type: number
|
|
description: Number of conversations resolved by the team during the date range
|
|
avg_resolution_time:
|
|
type:
|
|
- number
|
|
- 'null'
|
|
description: Average time (in seconds) to resolve conversations. Null if no data available.
|
|
avg_first_response_time:
|
|
type:
|
|
- number
|
|
- 'null'
|
|
description: Average time (in seconds) for the first response. Null if no data available.
|
|
avg_reply_time:
|
|
type:
|
|
- number
|
|
- 'null'
|
|
description: Average time (in seconds) between replies. Null if no data available.
|
|
example:
|
|
- id: 1
|
|
conversations_count: 250
|
|
resolved_conversations_count: 200
|
|
avg_resolution_time: 2800
|
|
avg_first_response_time: 240
|
|
avg_reply_time: 500
|
|
- id: 2
|
|
conversations_count: 180
|
|
resolved_conversations_count: 150
|
|
avg_resolution_time: 2400
|
|
avg_first_response_time: 200
|
|
avg_reply_time: 450
|