Dhairya-007 opened a new pull request, #29645:
URL: https://github.com/apache/camel/pull/29645

   Four option descriptions carry a misspelling or a duplicated word. Unlike a
   comment, an option description is user-facing: it is what the catalog, the
   reference documentation, the DSL Javadoc, the XSDs and tooling completion all
   show. Each fix is therefore applied to the declaration **and** to every
   generated copy of it, one commit per component.
   
   | Component | Option | Fix | Copies |
   |---|---|---|---|
   | netty | `maximumPoolSize` | `nettys` → netty's, `wont` → won't | 7 |
   | braintree | `settlementBatchSummary` | `wit` → with | 4 |
   | core-model (json dataformat) | `namingStrategy` | `the the` → the | 13 |
   | bean-validator | `validationProviderResolver` | `a a` → a | 6 |
   
   ### Keeping the generated copies exactly as the build would write them
   
   Maven cannot run in my environment, so the generated descriptors were updated
   by hand and each wrapped artifact was verified rather than guessed:
   
   - **Component DSL Javadoc** (`NettyComponentBuilderFactory`,
     `NettyHttpComponentBuilderFactory`) is machine-wrapped. I ported
     `EndpointDslMojo.formatJavadocOrCommentStringAsList` (greedy fill, break at
     the last space, width `78 - indent`) and confirmed that at width 69 it
     reproduces the existing paragraph byte-for-byte *before* applying the edit.
     The change lands on the final line, so the wrap is unchanged.
   - **XSD documentation** (`camel-xml-io.xsd`, `camel-spring.xsd`) is wrapped 
at
     120 columns — established by checking that the same algorithm reproduces 
all
     459 multi-line `CDATA` blocks of `camel-xml-io.xsd`. Removing `the ` from
     the `namingStrategy` text does let the next token move up, so those two
     blocks are re-wrapped as the generator would, not patched in place.
   - Each component descriptor and its `camel-catalog` copy were diffed after
     the edit and are byte-identical.
   
   ### Not changed
   
   `azure-storage-datalake` spells the option itself `retainUncommitedData`, and
   its `displayName` is derived from that name. Its *description* already reads
   "uncommitted" correctly, and renaming the option would break every route that
   sets it, so it is left as it is.
   


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