Replies: 1 comment
-
|
Apache Camel Karavan has always aimed to be a low-code integration platform that streamlines the full end-to-end experience for a broad range of developers. The Karavan Designer was originally an internal component, not intended to be a standalone, reusable module. We’ve now reached a point where upcoming next-generation features depend tightly on functionality already implemented in the main app. For that reason, the designer was merged into the Karavan app to allow us to continue delivering new capabilities effectively. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
I have seen the Karavan Designer is now moved inside the app in the latest code. Was there a reason outside streamlining the dev process / styles? We have seen the value of having it outside, as we can use the karavan-app to target developers and have access to all the tools, but we can also show outside of the karavan-app, the integrations, using the designer, so to target the power users, who want to do some small changes to integrations and flows, and they dont need to access everything.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions