Closed janydoe closed 2 days ago
Could you give me an example? Why is an identifier of the same name not enough?
There are no problems specifically for the code, but in the documentation (swagger, redoc, scalar) I would like to rename these fields so that there is no camelCase and it is understandable for people. Now we can name the key as follows: ["Session Cookie"], but then it will not be convenient in the code.
This is invalid token according OpenAPI spec
but you can annotate it with OpenAPI.Description
and get human readable description in UI ("Session Cookie description" line)
I see. Thanks
What is the problem this feature would solve?
now the open api displays the identifier that we specify as the key in security. and there is no way to rename it using the
HttpApiSecurity.annotate
orHttpApiSecurity.annotateContext
.What is the feature you are proposing to solve the problem?
Add the ability to change the identifier using the OpenApi.Identifier
What alternatives have you considered?
No response