Hi Ah yeah those were an idea to include the full page documentation in case tooling may be able to use that for something useable. However the tooling uses all the other bits, so we have just marked those apis as deprecated.
So we can remove the files from the camel-catalog. I have created a ticket to remove them https://issues.apache.org/jira/browse/CAMEL-16881 On Sun, Aug 22, 2021 at 9:48 AM Zoran Regvart <zo...@regvart.com> wrote: > > Hi David, > > On Sat, Aug 21, 2021 at 10:10 PM David Jencks <david.a.jen...@gmail.com> > wrote: > > > > I have a question about the purpose of the .adoc files in the catalog. The > > changes proposed here will remove the tables of options from these copies > > of the component .adoc files. These copies are already quite skimpy as > > they don’t successfully include the spring-boot information. > > > > What are these copies of the .adoc files supposed to be useful for? > > I think the catalog contains those so that an alternative UI can show > them, think tooltips or inline help in an IDE. I think, though I'm not > 100% sure that VSCode tooling is using that... > > > If there’s a desire to make them more complete, one strategy would be to > > build the components module of the website using a custom UI that has > > nothing in it, so we just get plain undecorated html pages, and putting > > those in the catalog. It would require some investigation, but it might > > conceivably be possible to arrange so links out of the components module go > > to the website rather than just be broken. > > I'd keep it as simple as it can be, so plain .adoc files, or if we > find out they're not used just remove them... > > 2c > > zoran > -- > Zoran Regvart -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
