-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider supporting Quarkus Dev UI in our extensions #2156
Comments
To hide an extension from the Dev console, it should be enough to remove the docs link from the metadata. We should consider doing it for at least those support extensions which expose no Quarkus configuration. |
There are 2 interesting ideas I have, but there are just ideas from a non frontend person, and I don't know if those are easy to tackle:
|
Camel 3.15 comes with API for developer console (camel-console JAR). It is an early prototype that comes with a set of out of the box consoles to provide various information about your running Camel application. More consoles will be added. These consoles currently are text based, but we need to spec the data in JSon so graphical consoles in camel-quarkus can use the data and display nicely. It seems the website has not updated yet with camel 3.15 docs, but there are some early details here |
@davsclaus Nice. I'd try to give the camel-console a look when I have time. |
I'm looking into this for a POC with camel-console, so I'm assigning myself. Let me know if you are working on this |
Since Quarkus 1.11.0.Final, there is Quarkus Dev UI, see https://quarkus.io/guides/dev-ui
It allows to quickly visualise all the extensions currently loaded, see their status and go directly to their documentation.
The good news is that the docs links work for Camel Quarkus extensions.
On top of that, each extension can add:
I wonder which of the above should we support?
See also quarkusio/quarkus#14471
The text was updated successfully, but these errors were encountered: