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

api-designreadabilityfunction-signaturenaming

Use a named-options object once a function exceeds ~3 parameters

Functions with more than about three positional parameters are hard to read and easy to misorder; pass a single options object with named fields instead.

PR: hegnar-journalist-boost · org-mining-2026-06Created: Jun 17, 2026

Bad example

Old codetypescript

1	`pushArticle(title, ingress, content, jwt, drpId, seoTitle, seoDesc, authorId, categoryId);`

Explanation (EN)

Objašnjenje (HR)

Good example

New codetypescript

1	`pushArticle({ title, ingress, content, jwt, drpId, seoTitle, seoDesc, authorId, categoryId });`

Explanation (EN)

Objašnjenje (HR)

Login required