Ricardo M.

If you don't mind @tplevko, I would like to keep this issue, because I think that it makes sense what you're mentioning, in the sense that this behavior might not...

Yes, the special handling is for the END steps: kamelet-sink is one of those steps: ``` name: "kamelet:sink" type: "END" id: "kamelet:sink-END" ``` that's why no other step can be...

There are two separate things going on here: 1. Whenever a new step is added, is not automatically selected, as the title states 2. On the other hand, even if...

Associated pull request: https://github.com/patternfly/react-log-viewer/pull/28

Hi @igarashitm, I think I understood the issue wrong, my bad. During Friday's conversation, we would to provide the same `Autoform` capability within step extensions, so this way we can...

I think that we have what we need already, we need to create a step extension that consumes the step id parameter and makes the HTTP call. The only bit...

I'm increasing the priority since it's touching several parts of the `VisualizationService` as many of the comparisons lead to `undefined` values.

This is still happening :)

Cool, thanks for sharing @mlorinc, I'll give it a try and see what happens.

This PR needs to be aligned with: * `@kaoto/uniforms-patternfly` * `@paternfly/react-core` * `@kie-tools-core/*`