Problem 1: In GraphQL, the shipping addresses are not returned as part of the Negotiable Quote object. Thus, the current state of a Negotiable Quote's shipping addresses cannot be determined. As a result, errors will be unknown to the user until they attempt to place an order, leading to a poor user experience.
Problem 2: In GraphQL, when setting a shipping address on a Negotiable Quote, we currently support only existing customer addresses from an address book. In order to maintain parity with Luma, we should allow the user to supply a new address for the Negotiable Quote.
Solution
Update the current schema so that the NegotiableQuote object includes its shipping addresses
Update the current schema so that the SetNegotiableQuoteShippingAddressInput object supports a new shipping address object
Problem
Problem 1: In GraphQL, the shipping addresses are not returned as part of the Negotiable Quote object. Thus, the current state of a Negotiable Quote's shipping addresses cannot be determined. As a result, errors will be unknown to the user until they attempt to place an order, leading to a poor user experience.
Problem 2: In GraphQL, when setting a shipping address on a Negotiable Quote, we currently support only existing customer addresses from an address book. In order to maintain parity with Luma, we should allow the user to supply a new address for the Negotiable Quote.
Solution
Update the current schema so that the NegotiableQuote object includes its shipping addresses Update the current schema so that the SetNegotiableQuoteShippingAddressInput object supports a new shipping address object
Requested Reviewers