This is not an implementation of tRPC because tRPC ues two methods: GET for queries and POST for mutations.
As an example, getting a list of notes (/v1/note/list) is impletmented as a POST instead of a GET

You're right that tRPC typically uses GET for queries and POST for mutations, but in this codebase, the API is built with tRPC and intentionally implements endpoints like /v1/note/list as POST mutations—even for data retrieval. This is documented in the OpenAPI metadata and is a design choice to support complex, structured input for filtering and searching notes. While this approach is consistent with the project's RPC-style API, it doesn't strictly follow either REST or standard tRPC conventions for HTTP methods. There isn't any explicit documentation or discussion in the codebase explaining this rationale, but the pattern is consistent across similar endpoints and appears to be intentional for flexibility and input handling.
See implementation details

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}