Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Not A Problem
-
3.4.4
-
None
-
None
-
Unknown
Description
It appears that the duplicate calls to OpenApiContext.read() are causing it to think the operationIds are duplicated, thus causing it to append a "_1" (or whatever the counter gets to) to the operationIds in order to make them unique.
Here's my understanding of what's causing the collisions:
In OpenApiCustomizedResource, it calls the OpenApiContext.read() operation here:
At the end of the method, though, it makes a call to the superclass' implementation of the getOpenApi() method here:
The overridden BaseOpenApiResource class' implementation of getOpenApi() subsequently calls OpenApiContext.read() again here:
It is during this second invocation of the OpenApiContext.read() method in the superclass where the operatorId collisions occur.
I am happy to submit a patch to address it, but I do ask for a little guidance here on how we'd like to fix this, please. It would seem that this would break existing behavior and I don't want to mess anyone up.
Thanks,
James