Dhairya-007 commented on PR #29645:
URL: https://github.com/apache/camel/pull/29645#issuecomment-6802269479

   Thanks — good catch, and fixed in the last push.
   
   The `@Metadata` literal concatenated `"...Property Naming Strategy."` with
   `"Possible values are:"` and lost the space between them, so every generated
   copy read "Strategy.Possible". The space is now added at the declaration
   (line 131 starts with `" Possible ...`) and in all 12 generated copies.
   
   Your note about the XSDs was exactly right: with the space the first `CDATA`
   line goes to 121 characters, so `LOWER_DOT_CASE,` moves down. Both
   `camel-xml-io.xsd` and `camel-spring.xsd` are re-wrapped accordingly rather
   than patched in place:
   
   ```
   -...Property Naming Strategy.Possible values are: LOWER_CAMEL_CASE, 
LOWER_DOT_CASE,
   -LOWER_CASE, KEBAB_CASE, SNAKE_CASE and UPPER_CAMEL_CASE.
   +...Property Naming Strategy. Possible values are: LOWER_CAMEL_CASE,
   +LOWER_DOT_CASE, LOWER_CASE, KEBAB_CASE, SNAKE_CASE and UPPER_CAMEL_CASE.
   ```
   
   The builder Javadoc at `:914` already had the space, so it is unchanged, and
   there is no `Strategy.Possible` left anywhere in the tree.
   
   On the annotation line itself: `:131` is now 144 characters, but it is a
   single string literal the formatter cannot split, and this file already has
   12 lines over 128 on `main` — the count is unchanged.
   


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