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
Additional context 1a9a1d4 appears to be the cause of this, which presumably was only supposed to filter out actuator endpoints that contained double asterisks, but is also filtering out non-actuator endpoints
The text was updated successfully, but these errors were encountered:
mc1arke
added a commit
to mc1arke/springdoc-openapi
that referenced
this issue
Feb 8, 2025
…gdoc#2895
All endpoints that contain a double-asterisks in the path are currently
being excluded from the output Swagger definition, rather than just
excluding match-all actuator endpoints. The endpoint matching is
therefore being altered to pre-filter the actuator endpoints to remove
any that contain a double-asterisks in the path, and remove the
subsequent filtering of double asterisks in the combined endpoints list
so that non-actuator endpoints aren't dropped by the actuator filtering.
Describe the bug
Since 2.7.0, a path that contains a double asterisk do not get included in the Swagger output.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
The endpoint to be included in the swagger output, e.g.
Additional context
1a9a1d4 appears to be the cause of this, which presumably was only supposed to filter out actuator endpoints that contained double asterisks, but is also filtering out non-actuator endpoints
The text was updated successfully, but these errors were encountered: