You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since 1.6.8 when using GroupedOpenApi.builder().addOpenApiCustomiser() multiple times, the customizers are executed in reverse compared to the previous version.
E.g. if i add customizer A and then customizer B i expect that A is executed first. However in 1.6.8 the order is reversed and B is called first.
I'm not sure if this is intended behavior or was introduced on accident.
The text was updated successfully, but these errors were encountered:
It was correctly introduced, to handle other cases ...
Maybe, we should preserve this order and accept that OpenApiCustomiser list will not be final.
I have made a change that could help handling other cases; without impacting the one you are mentionning.
Let me know if the last SNAPSHOT fixes the issue for you.
Since 1.6.8 when using
GroupedOpenApi.builder().addOpenApiCustomiser()
multiple times, the customizers are executed in reverse compared to the previous version.E.g. if i add customizer
A
and then customizerB
i expect thatA
is executed first. However in 1.6.8 the order is reversed andB
is called first.I'm not sure if this is intended behavior or was introduced on accident.
The text was updated successfully, but these errors were encountered: