omarsmak commented on pull request #5121: URL: https://github.com/apache/camel/pull/5121#issuecomment-785788213
> I think it is possible to have the same component with the new model, but I don't think we could introduce the usage of SDK without breaking the current behavior. If it is going to break the existing behavior, then definitely a new component with the SDK would make sense. Then I would at least rename this component to something like `camel-slack-legacy` and keep the new one with `camel-slack` to have it least confusing for the users. Of course this needs to be mentioned in the migration guides ---------------------------------------------------------------- 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
