nicolaferraro commented on issue #1980: URL: https://github.com/apache/camel-k/issues/1980#issuecomment-773191363
Yeah, the schema associated inline with the format was intended to be optional, present only if known in advance. When we think about sources I think there's no confusion: user chooses a `format` during binding and that's it. In general, we should validate there's only one dataFormat per <scope, format> pair. The problem arises when you think to sinks: a Telegram sink may accept an image, a video, a text or a structured JSON. We can let the user choose the `format` at binding time for the moment. But we can also think in the future to allow selecting all of them, or just a subset. But in general a sink may have multiple input types, that can be disambiguated at runtime via the `mediaType`. ---------------------------------------------------------------- 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
