Repository navigation
remove superfluous parameters at the mapping stage #327
Description
The mapping.yaml file currently allows adding extra parameters, e.g. a HttpServletRequest ..
For the client side in particukar, tt would also be usefult to generate interfaces in which named parameters coudl be dropped. These might represent common settings that are instead set by confiiguration or during initialisation, rathee than as part of each call, or just optional parameters the client does not send.
For example, something like:
map:
parameters:
- remove: traceLevel
Activity
hauner commentedon Mar 18, 2025
To make sure I understand your use case: For example: you have described a header in the OpenAPI that will be handled by a filter. Therefore it would not be needed in the endpoint interface method?
richard-melvin commentedon Mar 18, 2025
My use case is currently only for the client. On the server, I agree it could be handled by a filter, or perhaps could be bundled into some other added parameter.
hauner commentedon Mar 18, 2025
hmm, I'm confused by client side. openapi-processor does generate server side code. How do you use it client side? Feign? 🤔
richard-melvin commentedon Mar 18, 2025
I just wrote an implementaiton of the generated interface (using REST-assured).
hauner commentedon Mar 19, 2025
I'll add it.
parse drop mapping (openapi-processor/openapi-processor-spring#327)
fix test (openapi-processor/openapi-processor-spring#327)
add integration test (openapi-processor/openapi-processor-spring#327)
document removal of parameter (#327)
hauner commentedon Apr 21, 2025
available with 2025.2