oscerd commented on a change in pull request #5121:
URL: https://github.com/apache/camel/pull/5121#discussion_r585669211



##########
File path: 
catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/slack-component.adoc
##########
@@ -164,6 +168,35 @@ A CamelContext with Blueprint could be as:
 </blueprint>
 
---------------------------------------------------------------------------------------------------------------------------
 
+== Producer
+
+*Since Camel 3.9.0* +

Review comment:
       The since is not needed here. The documentation will be only for latest, 
so just remove the since, because the documentation is versioned

##########
File path: components/camel-slack/src/main/docs/slack-component.adoc
##########
@@ -164,6 +168,35 @@ A CamelContext with Blueprint could be as:
 </blueprint>
 
---------------------------------------------------------------------------------------------------------------------------
 
+== Producer
+
+*Since Camel 3.9.0* +

Review comment:
       Remove the since here, the other part will be re-generated

##########
File path: components/camel-slack/src/main/docs/slack-component.adoc
##########
@@ -180,6 +213,15 @@ You'll need to create a Slack app and use it on your 
workspace.
 
 Use the 'Bot User OAuth Access Token' as token for the consumer endpoint.
 
-IMPORTANT: Add the `channels:history` and `channels:read` user token scope to 
your app to grant it permission to view messages in the user's public channels.
+IMPORTANT: Add the corresponding history (`channels:history` or 
`groups:history` or `mpim:history` or `im:history`) and
+read (`channels:read` or `groups:read` or `mpim:read` or `im:read`) user token 
scope to your app to grant it permission to
+view messages in the corresponding channel. You will need to use the 
conversationType option to set it up too (`PUBLIC_CHANNEL`, `PRIVATE_CHANNEL`, 
`MPIM`, `IM`)
+
+*Since Camel 3.9.0* +

Review comment:
       Same




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


Reply via email to