Rules Hub
Coding Rules Library
← Back to all rules
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
backend ruleP2universalStack: REST / NestJS
api-designnamingrest
Name routes and endpoints after what they do
Endpoint paths should describe the resource/action (e.g. /user/live-data-optin), not internal implementation names. Clear, purpose-driven route names aid discoverability.
PR: hegnar-user-ws · org-mining-hist-2026-06Created: Jun 18, 2026
Bad example
Old codetypescript
| 1 | @Controller('api/user/zephrData') |
Explanation (EN)
Objašnjenje (HR)
Good example
New codetypescript
| 1 | @Controller('api/user/live-data-optin') |
Explanation (EN)
Objašnjenje (HR)