Repository navigation
Conversation
|
Hi @hemanth - thanks for the PR. JFYI - there are two other related PRs at play:
|
|
Hello @hemanth ! I see this PR holds changes to files that are probably unrelated to this specific PR. Can you please revert them? Thanks |
Add note (string, maxLength 500) to line_item.json for buyer-supplied per-item instructions (e.g. gift wrapping, dietary preferences, engraving text). - ucp_request: optional on create and update - Business echoes value in responses, MAY forward to fulfillment Closes Universal-Commerce-Protocol#349
c60a798 to
ca39d2d
Compare
|
Ah! Okies @damaz91 /me originally had these changes in one branch and split them into separate PRs, which has brought it side-effects. I have force-pushed the branch so it only touches |
|
Thanks for putting this together, @hemanth! Kitchen notes and dish modifications for prepared food landed with Food Checkout in #897, and retail item inputs like gift messages and engraving are being worked out on #915, where I've suggested standard optional fields for common inputs and extensions declared in the business profile for merchant-specific ones, so platforms know which items accept them. Closing this PR in favor of that work while keeping #349 open to track the use case, and we'd welcome your feedback on #915. |
Closes #349
Summary
Adds an optional
notestring field (max 500 chars) to the line item schema, allowing buyers to attach free-text per-item instructions.Use cases
Changes
source/schemas/shopping/types/line_item.json: Addednoteproperty withmaxLength: 500and appropriateucp_requestannotationsDesign decisions