I was reviewing the REST Node.js sample and comparing it against the official protocol specifications. I noticed two things:
1. Manual Typing in the Node.js Sample
Currently, the Node.js sample defines its UCP interfaces manually. Is there a specific reason for this? It seems like this sample should utilize the official @ucp-js/sdk.
2. Missing Catalog / Product Types in the SDK
I am looking to implement the Catalog Capability (dev.ucp.shopping.catalog), but I noticed these schemas are completely missing from the @ucp-js/sdk exports.
- The Node.js sample also omits the Catalog capability entirely.
- Without the SDK enforcing these types, it is unclear if merchants are expected to strictly follow the shape defined in the docs, or if the Catalog capability is still considered a draft/experimental feature.
Questions:
- Should a PR be opened to refactor the Node.js sample to use
@ucp-js/sdk?
- Is there an issue with the JSON schema generation for the
Catalog capability that is preventing it from being included in the SDK build?
I was reviewing the REST Node.js sample and comparing it against the official protocol specifications. I noticed two things:
1. Manual Typing in the Node.js Sample
Currently, the Node.js sample defines its UCP interfaces manually. Is there a specific reason for this? It seems like this sample should utilize the official
@ucp-js/sdk.2. Missing
Catalog/ProductTypes in the SDKI am looking to implement the Catalog Capability (dev.ucp.shopping.catalog), but I noticed these schemas are completely missing from the
@ucp-js/sdkexports.Questions:
@ucp-js/sdk?Catalogcapability that is preventing it from being included in the SDK build?