lburgazzoli edited a comment on issue #673:
URL: https://github.com/apache/camel-kamelets/issues/673#issuecomment-1006436054


   >     * AFAICT the user guide doesn't mention actions.  IIUC these have both 
a source and sink, so you can string them together.  An example in the user 
guide would be great.
   >
   
   The `kamelets`  documentation certainly need some refactoring and 
improvements but please bear in mind that `kamelets` are still  under heavy 
development. We are trying to make the `kamelets` and the related ecosystem a 
generic `camel` concept rather that a `camel-k` specific thing so there are 
things that are still missing or poorly documented. 
   
   However if you look at the 
[kamelet-component](https://camel.apache.org/components/3.14.x/kamelet-component.html)
 document, I think it is pretty easy to understand what the various actions 
types are meant to be used as they are pretty much like any other 
component/eip. 
   
   You are very welcome to improve the documentation to include a paragraph 
about actions.
    
   >     * The kamelets in the catalog have what appear to be toy sources and 
sinks.  Is their function for testing?  Mentioning this in the user guide might 
be helpful.
   > 
   
   It would be nice to report what the various sources and sinks are missing.  
   
   Bear in mind that `kamelets` are opinionated and aimed to hide the 
complexity of the underlying components/EIPs so  don't expect them to offer the 
same flexibility as the underlying components, if you need that flexibility 
then you probably should not look at `kamelets`.
   
   > 
   > I also think the description of extract field action is pretty close to 
useless.... "Extract a field from the body".... and then what? 
   
   I agree that in general there should be a better description of what an 
action is doing but about the `then what`, well it depends on what you want to 
achieve. Like when using the setHeader EIP you know that the EIP sets an 
header, that's all,  isn't it ?
   
   > Trying to find the source code behind this one, it appears to be in ` - 
"github:apache.camel-kamelets:camel-kamelets-utils:main-SNAPSHOT"` which I 
can't locate and which by the "main-SNAPSHOT" makes me wonder if it violates 
the Apache policy against directing people to unreleased code.
   > 
   
   The code is available in this repository, according to the doc 
[dependencies](https://camel.apache.org/camel-k/1.7.x/configuration/dependencies.html),
 the `github:` syntax is about using [jitpack](https://jitpack.io/) as a way to 
get the latest snapshot.
   


-- 
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


Reply via email to