Dhairya-007 opened a new pull request, #30100:
URL: https://github.com/apache/camel/pull/30100
## Problem
camel-stitch publishes a header `javaType` that names its class by simple
name only:
```
CamelStitchSchema StitchSchema or Map
```
`StitchSchema` is
`org.apache.camel.component.stitch.client.models.StitchSchema` - a class of
this component's own, in a nested `client.models` package that a reader would
not guess. It is the only header in the component whose type is not a built-in,
so it is the one entry in the table where the type carries information.
Fully qualified is the convention by a wide margin across the catalog: 3692
header `javaType` values are fully qualified or a built-in type, and 151 are
not.
## Fix
Qualify it, taking the FQN from the import the component's own sources use:
```
CamelStitchSchema StitchSchema or Map
-> org.apache.camel.component.stitch.client.models.StitchSchema or Map
```
Container spellings (`List`, `Collection`, `Map`) keep their bare form,
matching the rest of the catalog, and header names are untouched.
Metadata only - no behaviour change. I diffed the regenerated catalog file
against `main` and confirmed the listed `javaType` value(s) are the only fields
that differ.
--
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]