[ 
https://issues.apache.org/jira/browse/CAMEL-25411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-25411.
---------------------------------
    Resolution: Fixed

Fixed in https://github.com/apache/camel/pull/27486 (main e1bdb2f124b4).

> camel-jbang - Source editor: run the Kamelet checks the AI tools run
> --------------------------------------------------------------------
>
>                 Key: CAMEL-25411
>                 URL: https://issues.apache.org/jira/browse/CAMEL-25411
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.23.0
>
>
> The source editor of the Camel CLI validates a YAML file with the YAML DSL 
> schema (which knows the Kamelet envelope), the endpoint checks and the simple 
> checks. It does not run the Kamelet checks that camel_validate_source and 
> camel_write_file run (SourceValidator.validate with the file name), so it 
> reports none of these:
> * a Kamelet file with properties directly under spec (they go under 
> spec.definition)
> * a Kamelet template that starts from kamelet:<itself> instead of 
> kamelet:source
> * a route whose kamelet: endpoint has an unknown property (tagg for tag) or 
> leaves out a required one, checked against the catalog and the project's own 
> Kamelet files
> * a camel: dependency of a Kamelet file that the template does not use, and 
> camel:core (notes, CAMEL-25403)
> Verified with the custom Kamelet a local model wrote in the Kamelet side 
> check of the benchmark (tag-order-action): the AI tools report each case, the 
> source editor none.
> Proposal: the editor also runs KameletChecks: the shape of a .kamelet.yaml 
> and its template hints, and the kamelet: endpoints of a route file with the 
> project directory. The dependency notes are shown without blocking the save.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to