feat(viz) Replace Camel Route steps #288
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Nov 3, 2023
Currently, only CamelK Pipes support to replace nodes, leveraging source and sink placeholders. This commit adds the same functionality for Camel Routes fix: KaotoIO#79
lordrip
force-pushed
the
feat/replace-camel-route-step
branch
from
a279812 to
f958886
Compare
igarashitm
approved these changes
Nov 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
At this moment, only CamelK
Pipes supports node insite replacement.The goal for this pull request is to add said functionality for Camel Routes as well.
Changes
When removing the
fromnode from a Camel Route, it gets replaced with a placeholder, like thesourceandsinknodes from CamelKPipeWhen replacing the
fromnode from a Camel Route, the catalog only shows components that don't contain theproducerOnlytag.