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: language-agnostic

namingreadabilityclean-code

Avoid misleading qualifiers in names (mock, visible, ...)

Drop name qualifiers that no longer hold: don't call permanent data `*.mock`, and only call a subset `visibleX`/`filteredX` if a hidden/full set actually exists.

PR: hegnar-components · org-mining-hist-2026-06Created: Jun 18, 2026

Bad example

Old codetypescript

1	`import { categories } from './categories.mock'; // not actually a mock`
2	`const visibleCategories = categories; // nothing is hidden`

Explanation (EN)

Objašnjenje (HR)

Good example

New codetypescript

1	`import { categories } from './categories';`
2	`const categories = allCategories; // or keep 'visibleCategories' only if some are truly hidden`

Explanation (EN)

Objašnjenje (HR)

Login required