Dhairya-007 opened a new pull request, #29643:
URL: https://github.com/apache/camel/pull/29643
Camel's CI runs no spell checker, so misspellings have accumulated in Javadoc
and code comments. This corrects 114 of them in **main** sources across
`core/`, `components/`, `dsl/` and `tooling/`, one commit per area. Test
sources are left for a separate PR to keep this diff reviewable.
Comments only — no identifier, string literal or behaviour is touched, so
nothing here can affect compilation or a test.
Frequent ones: `implementators` → implementers, `convertable` → convertible,
`messsage` → message, `loosing` → losing, `lifecyle` → lifecycle,
`programatically` → programmatically, `splitted` → split, `seperate` →
separate, `paramter` → parameter, `exchnage`/`exchage` → exchange,
`definiton` → definition, `propgate`/`propogated` → propagate(d).
### How the list was built
`codespell` over every `*.java` file, then filtered to lines that are
comments (`//`, `/*`, `*`), then to entries where codespell offers a single
unambiguous correction. Each remaining word was checked against the generated
catalog with a word-boundary grep, so nothing here feeds a generated
descriptor.
### Deliberately excluded
- `iif` — a real Camel simple-language function (*inlined if*), documented in
`simple-functions.adoc`.
- `froms` — Camel's own plural of `from()`.
- `InOut`, `atMost`, `atLeast`, `afterAll`, `vertx` — Camel MEP names,
Awaitility and JUnit API names, and Vert.x.
- `Implementors`, `browseable`, `unparseable`, `useable`, `dependant` —
accepted variant spellings, not errors.
- `Uncommited` in azure-storage-datalake, `wont` in netty and netty-http, and
the bindy annotation Javadoc: those are option descriptions or feed
generated files, so they need the regenerated descriptors alongside and are
handled separately.
--
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]
