oscerd commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-2090933148
@davsclaus @zregvart this is working now and here is how it looks like:
https://camel.apache.org/camel-kamelets/next/aws-s3-source.html
So it will be enough to create a
oscerd commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-2090386674
This
https://github.com/apache/camel-kamelets/commit/c31b25a830413b8d22d52f229636b790842fdf6f
should fix that
--
This is an automated message from the Apache Git Service.
oscerd commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-2090356769
But then I'll have to do something like
`include::partial${name}-description.adoc[opts=optional]`
and it won't resolve the name part.
--
This is an automated
oscerd commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-2090318979
Ok, but the problem is it needs to be included in
https://camel.apache.org/camel-kamelets/next/aws-s3-source.html
Now I should be able to include it, but I'll have to
oscerd commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-2090302508
Yeah I fixed that but forget to update here
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
zregvart commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-2090288847
@oscerd the page is here:
https://camel.apache.org/camel-kamelets/next/aws-s3-source-description.html
--
This is an automated message from the Apache Git Service.
To
oscerd commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-2090043833
I tried to add this file
https://github.com/apache/camel-kamelets/blob/main/docs/modules/ROOT/pages/aws-s3-source-description.adoc
And add the include in the template
zregvart commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-2051394135
> Do you have eventually time to draft something we could start to hack on?
Like a branch with just one adoc ported? Thanks.
Unfortunately, I don't see much free time
oscerd commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-2050971678
> > Do you think is feasible to go away from js generation on-the-fly and
have generated .adoc directly in the repository?
>
> It is very much feasible, this is what we
zregvart commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-2036597946
> Do you think is feasible to go away from js generation on-the-fly and have
generated .adoc directly in the repository?
It is very much feasible, this is what we do
oscerd commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-2036205392
I would like to restart the discussion on this but we need some help from
@zregvart
Do you think is feasible to go away from js generation on-the-fly and have
oscerd commented on issue #1705:
URL:
https://github.com/apache/camel-kamelets/issues/1705#issuecomment-1787691418
The main problem is understanding if we can move away from the js generation
for the docs example. Because actually we're using that stuff with a template.
--
This is an
davsclaus opened a new issue, #1705:
URL: https://github.com/apache/camel-kamelets/issues/1705
Kamelets are universal connectors for Camel, and we should tidy up docs and
make it more user focused and less tech savy.
The knative binding stuff should be removed. This kind of docs
13 matches
Mail list logo
