-
Notifications
You must be signed in to change notification settings - Fork 152
PromptBuilder doesn't surface the Catalog's id #900
Copy link
Copy link
Open
Labels
P1A high-priority issue. Someone should be assigned and actively working on it.A high-priority issue. Someone should be assigned and actively working on it.front-line-handledCan wait until the second-line triage. The front-line triage already checked if it's a P0.Can wait until the second-line triage. The front-line triage already checked if it's a P0.second-line-triagedThe issue has been fully triaged.The issue has been fully triaged.
Metadata
Metadata
Assignees
Labels
P1A high-priority issue. Someone should be assigned and actively working on it.A high-priority issue. Someone should be assigned and actively working on it.front-line-handledCan wait until the second-line triage. The front-line triage already checked if it's a P0.Can wait until the second-line triage. The front-line triage already checked if it's a P0.second-line-triagedThe issue has been fully triaged.The issue has been fully triaged.
Describe the bug
When creating the system prompt using a custom
Catalog, the system prompt doesn't contain the catalog's id.But then in the
CONTROLLING_THE_UIsection, the prompt says:use the catalog ID provided in system instructions.The only catalogId in the instructions is in the first example from BasicCatalog (if you include that), which is:
{ "version": "v0.9", "createSurface": { "surfaceId": "main", "catalogId": "https://a2ui.org/specification/v0_9/standard_catalog.json", "sendDataModel": true } }So then, during building of the widgets, the controller throws an error because no such catalog exists.
Also, https://a2ui.org/specification/v0_9/standard_catalog.json is a HTTP 404.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The prompt states which catalog id the app expects.
Also, possibly,
catalogIdshould be a required field onCatalog?// cc @redbrogdon