djencks commented on issue #1795: URL: https://github.com/apache/camel-quarkus/issues/1795#issuecomment-693490444
> On Sep 16, 2020, at 12:00 AM, Peter Palaga <notificati...@github.com> wrote: > > > I recommend generating the json file into modules/ROOT/examples > > Hm... why examples? The data is not examples. I think catalog or similar would describe better what's inside. > > Probably I wasn’t clear enough… the best family for this sort of file is ‘example’. You can name the file anything, e.g. `modules/ROOT/examples/catalog.json` > I thought I had more examples handy, and don’t have time to construct any right now, but if you create the json file > > Yes, I can do that, but when you speak about a json file in sigular, does that mean that there has to be a single file? I'd prefer having one JSON file per table row. That will allow us to avoid merge conflicts when people are going to work on various extensions in parallel. > > At the moment, there needs to be only one json file. I can consider querying the content catalog for multiple files, but I’m not quite convinced it’s a good idea yet, and it would certainly be a significant amount of work. Maybe there’s some adoc file from which the information can be extracted? Perhaps the component page in the main camel docs? Or if there is at most one component per extension, perhaps the info could go into the extension pages? > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <https://github.com/apache/camel-quarkus/issues/1795#issuecomment-693214444>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAELDXWWKGLR4D4SNGMSS3LSGBO7XANCNFSM4RNIINJQ>. > ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
