Dennis Melzer

Should this not be a MultipartFileResource? https://docs.spring.io/spring-framework/docs/5.1.8.RELEASE_to_5.1.9.RELEASE/Spring%20Framework%205.1.9.RELEASE/org/springframework/web/multipart/MultipartFileResource.html See source: https://github.com/spring-projects/spring-framework/blob/main/spring-web/src/main/java/org/springframework/web/multipart/MultipartFileResource.java

Hey @martin-mfg Iam unsure if really Resource is right for a Multipart. I don't know why the other API are using it. We are using MultipartFile and there is method...

Currently we have Spring Api with MultiPart. I can check my settings and which version. We also use the generated Spring Client. So this will then break our current Api...

That's the generated code with open api generator 7.5.0 Spring Java ``` @RequestMapping( method = RequestMethod.POST, value = "/packages", produces = { "application/json" }, consumes = { "multipart/form-data" } )...

Hi, I would vote for this feature, for me its more a bug :), because the older cli supported this feature that you have no deps inside the HTML. This...

Is there an update and a solution here? if not does anyone have an example of what to implement exactly? The example with the gateway didn't get me any further...

@mxmlnglt yes a POC works with this approach. Did not try what happen if the token is expired, but IMHO would that be a good general interceptor, but ok.

@mikeut I think you are in the wrong issue tracker, this is related to the open api generator project. And yes, org.springframework.cloud.security.oauth2.client.feign is no longer used there.

From my point of view, you/we should basically think again about the `JsonNullable`. In my use cases it would make sense to return `Optional` everywhere except for the PATCH endpoints...

> I think if it's valid for PATCH it's valid for POST as well. Some projects just use POST instead of PATCH - even it it's not "correct" Yeah you...