Reading — Blazor, Held Together

Blazor, Held TogetherComponent Discipline · Rule 1

Component Discipline

Rule 1Chapter I

Components own their markup; services own their logic.

Why this rule exists

A component that fetches, transforms, caches, and renders is four responsibilities in one file — and each one makes the others harder to test and reuse.

Blazor, Held Together

In practice

If a method in a .razor file does not touch rendering, it belongs in an injected service. The component keeps parameters, UI state, and event plumbing; everything else moves out.

When it doesn't apply

Tiny leaf components can inline trivial logic — extracting a one-liner is ceremony, not architecture.

Related rules

2Parameters flow down; EventCallbacks flow up.Supports

Keep reading

3 of 12 · 18%