Skip to content

After P -> A -> B flow, OrderItems in B response are missing various properties including accessPass #120

Open
@lukehesluke

Description

@lukehesluke

Missing fields

  • position
  • (for virtual sessions)
    • accessChannel
    • customerNotice
  • (for physical sessions)
    • accessPass
    • accessCode
  • (not OrderItems but the Orders themselves):
    • totalPaymentTax (i haven't checked for all of them, but I can confirm that this was available in P's response - just not B. I expect they're all like that)
    • customer.identifier (it seems like all Customer fields excepting @type and email are missing from the B-after-P response)
    • customer.familyName
    • customer.givenName
    • customer.telephone
    • payment (therefore, payment reconcilliation tests fail)

An example failing test output:

access-channel_includes-access-channel-or-customer-notice_OpenBookingApprovalFlow_ScheduledSession.md

This error:

* ❌️ should include an `accessChannel` or a `customerNotice`
    - TypeError: Cannot read property 'accessChannel' of undefined

is because the test looks for OrderItem with position: 0 and it does not find it. The result has no position.

However, it also would have failed even still as the result has neither an accessChannel or a customerNotice - at least one of which is expected

This makes the following tests fail in Approval mode:

  • includes-access-channel-or-customer-notice
  • manual-access-codes
  • access-barcode-seller
  • access-pass-image
  • access-code-update-notifications
  • access-pass-update-notifications
  • customer-notice-notification
  • business-to-business-tax-calculation-net
  • business-to-consumer-tax-calculation-net
  • fail-outside-window
  • succeed-within-window
  • atomic-cancel
  • book-and-cancel
  • patch-contains-excessive-properties-error
  • patch-not-allowed-on-property-error
  • ...and some more

Metadata

Metadata

Assignees

Labels

approval-flowNeeded for Approval Flow to work across test

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions