Currently, operationId is set from the name that is decorated. This means that web.View methods all receive the same ID. This results in every endpoint in that class opening/closing in the swagger UI when any one is clicked, due to them all having the same id attribute.
The same issue could happen if a user utilises the same handler function for multiple paths in the router.
Currently, operationId is set from the name that is decorated. This means that web.View methods all receive the same ID. This results in every endpoint in that class opening/closing in the swagger UI when any one is clicked, due to them all having the same id attribute.
The same issue could happen if a user utilises the same handler function for multiple paths in the router.