gnodet-bot commented on code in PR #27168:
URL: https://github.com/apache/camel/pull/27168#discussion_r4154435970
##########
components/camel-odata/src/main/docs/odata-component.adoc:
##########
@@ -0,0 +1,408 @@
+= OData Component
+:doctitle: OData
+:shortname: odata
+:artifactid: camel-odata
+:description: Camel OData Component
+:since: 4.23
+:supportlevel: Preview
+:tabs-sync-option:
+:component-header: Only producer is supported
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The OData component allows you to interact with OData V4 services using
standard OData CRUD operations.
+
+The component provides OData-specific request and response handling while
using Camel HTTP as the underlying HTTP transport.
+
+The OData component is the successor to the deprecated `camel-olingo4`
component.
+
+The component supports OData V4 services using JSON representations.
+
+Maven users will need to add the following dependency to their `pom.xml` for
this component:
+
+[source,xml]
+
+<dependency>
Review Comment:
🔴 **AsciiDoc listing blocks need opening `----` delimiters.** Every
`[source,*]` block in this file is missing its opening `----`. The AsciiDoc
spec requires both an opening and closing `----` around the content when using
listing block syntax.
For example, this block (and all 16 others like it) should be:
```suggestion
[source,xml]
----
<dependency>
```
The current pattern — `[source,xml]` followed by a blank line and then
content — causes the Antora renderer to produce the `unterminated listing
block` warning that the docs CI job already flagged (see @apupier's comment).
The same fix is needed for all 17 `[source,*]` blocks in the file: lines 25,
43, 106, 114, 195, 241, 253, 261, 280, 300, 316, 336, 348, 358, 364, 376, 392.
Five of those blocks (114, 241, 253, 300, 358) are also missing a closing
`----`.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
