gen-spec.ts does not follow the OpenAPI specification, giving the same operatorId

[Lhcfl]

💡 Summary

gen-spec.ts does not follow the OpenAPI specification, giving the same operatorId, which causes problems when viewing api doc using other tools (such as Elements)

https://github.com/misskey-dev/misskey/blob/develop/packages/backend/src/server/api/openapi/gen-spec.ts#L214

operationId is an optional unique string used to identify an operation. If provided, these IDs must be unique among all operations described in your API. https://swagger.io/docs/specification/paths-and-operations/

🥰 Expected Behavior

get and post should use different operatorId

🤬 Actual Behavior

gen-spec.ts does not follow the OpenAPI specification, giving the same operatorId, which causes problems when viewing api doc using other tools (such as Elements)

An example is:

"/emoji": {
            "get": {
                "operationId": "emoji",
                 // ...
            }
            "post": {
                "operationId": "emoji",

📝 Steps to Reproduce

No response

💻 Frontend Environment

No response

🛰 Backend Environment (for server admin)

No response

Do you want to address this bug yourself?

• Yes, I will patch the bug myself and send a pull request

[Sayamame-beans]

related: #13498

[kakkokari-gtyih]

Duplicate of #13498