Repository navigation
NO-TICKET: Fix itinerary transportation_type documented values - #135
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedThis review ran on the open-source allowance, not this organization's plan, because the pull request author doesn't have an assigned seat. Waiting won't change this — ask an organization admin to assign them a seat, or add seats in Billing if every seat is already assigned, then retry. Next included review available in 36 minutes. View limit details
No actionable comments were generated in the recent review. Summary
Change: Other Merge Risk:
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
clue-gyg
left a comment
There was a problem hiding this comment.
✅ Auto-approved
The change is documentation-only, 4 lines in spec/components/schema/itinerary.yaml. It updates one field's description text and its example value (bus → bus_coach). The type, nullability and validation are unchanged, so the API contract is not altered.
The documented list (bus, boat, plane, walking, …) never occurs. The field has the same type as the option-level transportation mode, and all 57 values in the 2026-11-04 export are in that list (e.g. speed_boat, golf_cart, dhow). Nothing validates against the list, so the doc says so. Raised by Trip.com.
🤖 Generated with Claude Code