-
Notifications
You must be signed in to change notification settings - Fork 32
[BUG] Branches are removed in VS Code #513
Comments
Reproduced with standalone - if you look at the source code, the step in |
How are you adding the branches? Using the step extension? |
Reproduced with an unit test that a branch step disappears by POSTing a |
Turned out this won't happen once KaotoIO/kaoto-ui#1381 is solved. |
it is still happening. I guess the |
Agreed solution: |
So when user adds 3 |
Yes, it will be. |
For after release 1.0.0 maybe we can introduce something else on branches to be more accurate. |
I would say, this will be a bug since it's against what user want to do. IMO we should disable to modify the branch at backend side until these unexpected behaviors are sorted. |
But it is not modify, it is interpreting from the JSON |
(on hold I have a zombie of Kaoto backend reunnign somewhere) EDIT: exact same behavior with latest Kaoto Backend from main branch than in this comment #513 (comment) |
response to the request on http://localhost:8081/v1/integrations?dsl=Camel%20Route goes from:
to
|
But do the canvas show something different? |
now the canvas is keeping the step configure din the otherwise. But there are no ways to add a when using the UI. |
I see, on the source code we are removing branches without conditionals when syncing. |
Describe the bug
Branches are removed in VS Code
To Reproduce
Steps to reproduce the behavior:
Expected behavior
previous branch is kept
Logs
I think it is due to this kind of request returning a wrong result:
http://localhost:8081/v1/integrations?dsl=Camel%20Route
with payload (with the 2 branches and oen with a component):
give response without the component:
Environment (please complete the following information):
Additional context
initial issue KaotoIO/vscode-kaoto#168
The text was updated successfully, but these errors were encountered: