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

Claus Ibsen updated CAMEL-25897:
--------------------------------
    Description: 
CAMEL-25892 brought the body types each step of a route has been reached with, 
across the messages (CAMEL-25750), to the Routes and Diagram views of {{camel 
tui}}. This issue is its third view, the source editor:
* a dimmed hint at the end of the line of each step with its body types;
* a ⚠ in the gutter of a step reached with bodies of more than one kind (null, 
payload, data or collection), which needs attention.

{noformat}
   7          - unmarshal:                       ByteArrayInputStreamCache
   8              json: {}
   9          - choice:                          LinkedHashMap
  ...
⚠ 18          - to: file:outbox                  byte[] | LinkedHashMap  
(payload and data)
{noformat}

The facts of a line only hold while the editor has the version of the file that 
runs. The Source tab knows that from the run state of CAMEL-25771 (whether the 
integration runs the file as saved), and leaves the hints out until it does.

Scope change: keeping the hints of the routes an edit did not change, by their 
checksums, is not part of this issue. The TUI cannot compute the checksums of 
the routes of an edited YAML or XML file: loading the file with Camel runs 
parts of it (its beans), and an endpoint written with parameters is built by 
its component, which the TUI does not have. See 
https://github.com/apache/camel/pull/28234.

_Filed by Claude Code on behalf of davsclaus_

  was:
CAMEL-25892 brought the body types each step of a route has been reached with, 
across the messages (CAMEL-25750), to the Routes and Diagram views of {{camel 
tui}}. This issue is its third view, the source editor:
* a dimmed hint at the end of the line of each step with its body types;
* a ⚠ in the gutter of a step reached with bodies of more than one kind (null, 
payload, data or collection), which needs attention.

{noformat}
   7          - unmarshal:                       ByteArrayInputStreamCache
   8              json: {}
   9          - choice:                          LinkedHashMap
  ...
⚠ 18          - to: file:outbox                  byte[] | LinkedHashMap  
(payload and data)
{noformat}

The facts of a line only hold while the editor has the version of the file that 
runs. Once the file is edited, the routes that did not change can keep their 
hints. Knowing which routes did not change needs the route checksum of 
CAMEL-25771, so this waits for it.

_Filed by Claude Code on behalf of davsclaus_


> camel-jbang - show the body types each step has been reached with in the 
> source editor
> --------------------------------------------------------------------------------------
>
>                 Key: CAMEL-25897
>                 URL: https://issues.apache.org/jira/browse/CAMEL-25897
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.24.0
>
>
> CAMEL-25892 brought the body types each step of a route has been reached 
> with, across the messages (CAMEL-25750), to the Routes and Diagram views of 
> {{camel tui}}. This issue is its third view, the source editor:
> * a dimmed hint at the end of the line of each step with its body types;
> * a ⚠ in the gutter of a step reached with bodies of more than one kind 
> (null, payload, data or collection), which needs attention.
> {noformat}
>    7          - unmarshal:                       ByteArrayInputStreamCache
>    8              json: {}
>    9          - choice:                          LinkedHashMap
>   ...
> ⚠ 18          - to: file:outbox                  byte[] | LinkedHashMap  
> (payload and data)
> {noformat}
> The facts of a line only hold while the editor has the version of the file 
> that runs. The Source tab knows that from the run state of CAMEL-25771 
> (whether the integration runs the file as saved), and leaves the hints out 
> until it does.
> Scope change: keeping the hints of the routes an edit did not change, by 
> their checksums, is not part of this issue. The TUI cannot compute the 
> checksums of the routes of an edited YAML or XML file: loading the file with 
> Camel runs parts of it (its beans), and an endpoint written with parameters 
> is built by its component, which the TUI does not have. See 
> https://github.com/apache/camel/pull/28234.
> _Filed by Claude Code on behalf of davsclaus_



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

Reply via email to