bartoszpop opened a new pull request, #1664: URL: https://github.com/apache/camel-karavan/pull/1664
**Title:** feat(vscode): support file and HTTP Kamelet catalogs ## Summary Extend `Karavan.kameletsPath` to load editor Kamelet catalogs from local directories, individual YAML files, and HTTP(S) URLs. - Support multiple Kamelets per file, including LF and CRLF line endings, comments, directives, and empty documents. - Parse built-in catalogs using the same YAML document parser, fixing Windows loading failures caused by LF-only splitting. - Add a 30-second remote-loading timeout and report HTTP, network, and YAML errors while keeping the built-in catalog available. - Separate editor catalog configuration from Camel JBang runtime configuration. - Fix **Custom only** filtering so it preserves selected categories and applies consistently to regular and preferred cards. ## Configuration and migration `Karavan.kameletsPath` is now **editor-only**, including directory sources. It is never passed to Camel JBang or downloaded into the integration project. Use the new `camel.localKameletDir` setting for `--local-kamelet-dir` during run/export, including runtime run and deploy. It accepts only an existing local directory. **Existing users relying on `Karavan.kameletsPath` for runtime Kamelets must also set `camel.localKameletDir`.** Reopen the designer after changing the editor catalog setting. ## Validation - All 17 targeted tests pass: `npm run test:kamelets`. - Production bundles build successfully: `npm run package`. - Type-checking reports the same 15 pre-existing errors, with no new diagnostics. Regression coverage includes the shipped 250-Kamelet catalog with both line endings, multi-document sources, HTTP redirects and failures, timeout handling, runtime-setting validation, and reversible **Custom only** filtering. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
