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).

PriorityP2 — style, consistency, readabilityScopeUniversal — language-agnostic, broadly applicable

Exceptions / tradeoffs (EN)Iznimke / tradeoffi (HR)

fullstack ruleP2universalStack: universal

code-reviewcollaborationpragmatism

Do not block a PR over equivalent stylistic choices

If two approaches are functionally equivalent and equally readable, don't force your style on the author; reserve change requests for issues of correctness, separation, or testability.

PR: frontpage-web · org-mining-hist-2026-06Created: Jun 18, 2026

Bad example

Old codetext

1	`// 10+ review comments insisting an equivalent render method be inlined as a component`

Explanation (EN)

Objašnjenje (HR)

Good example

New codetext

1	`// Request changes for correctness/separation/testability; accept equivalent style choices and move on`

Explanation (EN)

Objašnjenje (HR)

Login required