oscerd commented on issue #673: URL: https://github.com/apache/camel-kamelets/issues/673#issuecomment-1007157005
You weren't asking for this fix, but for something else, using the extract action for setting the indexId from the json routing in the integration. This is not a solution, it's just a workaround. Thanks for reporting about the links, I'll take care of fixing them. Maybe there were some updates when we changed the way the documentation generation with some PRs from David. I will always speak up when the work from this community and from the oldest contributors will be underrated and I really wish that members of this PMC do the same, because in the last weeks I just seen attempts to criticize the work done and find faults in what it is done (if someone feel I'm talking about him, yes, I'm talking about you, David). 20 hours ago I couldn't answer about the fix, because your problem was and it's still different. The 100's hours of time you consumed, it's 500 hours of work done from contributors around Kamelets and camel-k. The fact that you don't know the code or you have troubles finding where the code is or how it is working, it's part of the game. Camel is a really complex ecosystem, documenting everything will always be impossible, given the number of real contributors working regularly and with passion on this. I'll take comments like yours as offence, because you and many others, consider, ALWAYS, our time for granted, which it's wrong and unpleasant to read. That say, thanks for your feedback and I'll trying to improve the upstream documentation, in my spare time, as always. -- 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. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
