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

   # Description
   
   Part of [CAMEL-23832](https://issues.apache.org/jira/browse/CAMEL-23832). 
This pull request covers `camel-alibaba-ots` (scheme `alibaba-ots`). It does 
not complete the ticket, so please keep the ticket open.
   
   This is a follow-up to #29991, which improved the option and header 
descriptions of `camel-alibaba-ots`. It changes one text: the 
`CamelAlibabaOtsOperation` header gets a third sentence, so that it reads the 
same as the fc header texts merged with #30004.
   
   In the review of #30004 (`camel-alibaba-fc`), the reviewer pointed out that 
the option texts name the fallback to an exchange property of the same name, 
while the header texts said only that the header replaces the option, and asked 
to align them. That pull request added this sentence to the fc header texts. 
The ots header text merged with #29991 has the same gap: the text of the 
`operation` option names the exchange property, but the text of the 
`CamelAlibabaOtsOperation` header does not.
   
   The new text:
   
   > The operation that the producer performs. This header replaces the 
operation option. If this header is not set, an exchange property of the same 
name replaces the operation option.
   
   Only this description text changes. No option or header is added, removed or 
renamed, and no default value, label, type or enum value changes. The text is 
in the `description` attribute of the `@Metadata` annotation on the header 
constant `OPERATION` in `AlibabaOtsHeaders`, where the old text already was. 
The component JSON, its copy in `catalog/camel-catalog` and 
`AlibabaOtsEndpointBuilderFactory` in `dsl/camel-endpointdsl` are regenerated. 
The doc page lists the headers from the component JSON 
(`include::partial$component-endpoint-headers.adoc[]`), so it does not change.
   
   | Text | Problem in the current text | Checked against |
   |---|---|---|
   | `CamelAlibabaOtsOperation` (header) | It does not say that an exchange 
property of the same name replaces the operation option when the header is not 
set, although the text of the `operation` option says so. | 
`AlibabaOtsProducer.process`, `AlibabaOtsUtils.createClientConfigurations`, 
camel-alibaba-common `OpenApiClientSupport.resolveString` (the header, else the 
exchange property of the same name, else the option), `AlibabaOtsHeaders` and 
`AlibabaOtsProperties` (the name CamelAlibabaOtsOperation); the fc header texts 
merged with #30004 (`FCHeaders`, the same third sentence with the fc option 
names); no test sets the header or the exchange property, so this rests on 
reading the code |
   
   # Target
   
   - [x] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   
   - [x] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   # Apache Camel coding standards and style
   
   - [x] I checked that each commit in the pull request has a meaningful 
subject line and body.
   - [x] I have run `mvn clean install -Dquickly -DskipTests` from the root 
folder on 31e144597200, the parent of the commit in this pull request, and then 
`mvn install -DskipTests -nsu` in `components/camel-alibaba/camel-alibaba-ots`, 
`catalog/camel-catalog` and `dsl/camel-endpointdsl`, and I have committed all 
auto-generated changes.
   
   # AI-assisted contributions
   
   - [x] If this PR includes AI-generated code, commits have proper 
co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR 
description identifies the AI tool used.
   
   The change and this text were made with Claude (Anthropic), and the new 
sentence was checked against the Camel source.
   
   _Claude Code on behalf of saravanakumar1987_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


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