WMK666666 opened a new pull request, #29720:
URL: https://github.com/apache/camel/pull/29720

   Follow-up to #29594, as suggested in its review: `outputFormat` still lists 
`html_split_page` in its `enums`, and that value cannot produce anything.
   
   * With `useDoclingServe=true`, #29594 makes the request fail, because 
`DocumentResponse` has no field for the split pages.
   * On the CLI path the option is never read either: every operation passes 
its own format (`DoclingProducer.java:309-353`, `:717`).
   
   So the option description now says so, and the component metadata is 
regenerated.
   
   ```
   @Metadata(description = "Output format for document conversion. The 
html_split_page value is rejected
             when useDoclingServe is true, as docling-serve returns no split 
pages, and the CLI operations
             pass their own format; use html instead", ...)
   ```
   
   **Merge order:** this only documents the behaviour that #29594 introduces, 
so it should go in after #29594. On its own the description would be a step 
ahead of `main`.
   
   **On the regenerated file:** `docling.json` gains exactly the same sentence 
in both places the option is described (`componentProperties` and 
`properties`), nothing else. I ran the generator and then kept only the two 
strings this change touches — the `4.24.0-SNAPSHOT` plugin I have locally also 
re-adds an empty `deprecationNote` to every property, which `main`'s committed 
file does not carry, so a full regeneration from my side would have added ~143 
lines of generator-version noise to this PR.
   
   `formatter:validate` and `impsort:check` pass, and the module compiles.
   


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

Reply via email to