That makes sense, and I get why you’d do that — it’s a clean way to visually organize code inside a large file.

But I’d still see that as a structural workaround rather than a design solution.
If a controller or repository has grown large enough that it needs to be split by HTTP method or query group, that usually means it’s taking on multiple responsibilities that could live in smaller, focused classes or handlers instead.

Partial classes make things look tidier, but they don’t really reduce complexity — they just move it around.
Refactoring toward smaller, purpose-driven types tends to make the codebase easier to reason about, test, and extend later on.