umbraco-review-checks

You can review Umbraco backoffice extensions by applying comprehensive code quality, architecture, and UI pattern checks that validate repository patterns, workspace context consumption, localization, and property editor schema alias correctness to prevent regressions.

Common Umbraco architecture checks detect direct API access from UI components, missing workspace context, absent repository layers, inconsistent persistence patterns, and circular context dependencies to enforce proper separation of concerns.

Validating Umbraco property editor schema aliases involves enforcing specific technical rules during code review to ensure correct alias mapping and proper schema usage within the backoffice extension architecture.

Yes, the code review process applies to various Umbraco extension types including dashboards, workspaces, property editors, entity actions, and context or repository components, mapping extension elements to the correct check categories.

Umbraco backoffice UI pattern checks verify correct error handling via notifications, proper workspace layout usage, correct UUI component usage, enum and select handling, accessibility, loading states, and enforce avoiding inline styles.

Umbraco extensions fail code review checks when they bypass reactive state patterns, skip context APIs, use direct service access from UI layers, or implement incorrect property editor schema aliasing instead of following established architecture patterns.