Kaynağa Gözat

fix: update stale Booking.com GraphQL client-version and timeout

Drift audit (scripts/har_audit.py) against a comprehensive Booking
HAR found apollographql-client-version and
x-envoy-expected-rq-timeout-ms stale for updateRoomDateMutation and
messaging ops. inventory/fetch and inventory/update (used elsewhere
by get_calendar/set_price) no longer appear in any capture -- the
live UI has moved those to GraphQL; that migration is scoped
separately and not included here.
ZiB 5 gün önce
ebeveyn
işleme
0df95431fe
1 değiştirilmiş dosya ile 3 ekleme ve 3 silme
  1. 3 3
      room_cal/service_api/_booking.py

+ 3 - 3
room_cal/service_api/_booking.py

@@ -30,9 +30,9 @@ _SENDER_LABELS: dict[str, str] = {'GUEST': 'Guest', 'PARTNER': 'Host'}
 
 # Sync with scripts/har_audit.py via DRIFT_MANIFEST below — these are the only
 # copies; the manifest references them rather than duplicating the literals.
-_GQL_CLIENT_VERSION = 'EQSXMHMY'
-_GQL_TIMEOUT_MS = '15000'
-_MSG_CLIENT_VERSION = 'ABJaNSUc'
+_GQL_CLIENT_VERSION = 'cfJLLJeC'
+_GQL_TIMEOUT_MS = '60000'
+_MSG_CLIENT_VERSION = 'EQDFPbZe'
 
 _UPDATE_MUTATION = """mutation updateRoomDateMutation($input: PartnerAvailabilityUpdateInput) {
   partnerAvailabilityMutations {