-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Desktop json recipes upload #4629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| throw new Error( | ||
| `Failed to parse ${isJsonFile ? 'JSON' : 'YAML'} file: ${error instanceof Error ? error.message : 'Invalid format'}` | ||
| ); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yaml is a superset of json, so no need to parse them separately. more problematically though, recipes are not always correct yaml before parameter substitution. I don't think the client should do any parsing here really
| throw new Error(`${isJsonFile ? 'JSON' : 'YAML'} file is empty or contains invalid content`); | ||
| } | ||
|
|
||
| // Handle both CLI format (flat structure) and Desktop format (nested under 'recipe' key) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove this comment or update it about legacy; there should be no Desktop format
* main: Soften str_replace instructions for weaker LLMs (#4639) docs: changed logo (#4633) Add `analyze` tool to Developer extension (#4530) Add recipe title in import form (#4625) Desktop json recipes upload (#4629) Catch errors in node main (#4627) chore(deps-dev): bump vite from 7.1.3 to 7.1.5 in /ui/desktop (#4583) docs: add Rube extension documentation and server configuration (#4556) Always show recipe activities at the top of chat when recipe accepted and active (#4616) Add parameter replacement to activities in ui (#4617) UI recipes filter invalid, duplicate and unused params (#4615) Fix gpt-5 input context limit (#4619) [docs] MCP-UI Blog Post (#4578) release/1.8.0 (#4577) fix: docker build include valid string prior to sha (#4613) Run the conversation fixer over messages for recipe create (#4605) docs: github copilot config workarounds (#4607) Add recipe schema validation to UI (#4602)
Signed-off-by: HikaruEgashira <[email protected]>
Follow up from #4544 to also allow json recipe uploads