sage-review-code

To check React component pattern violations before opening a PR, you can review changes for propTypes, forwardRef usage, classnames patterns, and configs.js exports. This ensures compliance with established conventions and provides actionable, structured feedback.

The best way to identify gaps in Jest test coverage for sage-lib components is to run a targeted file review that flags missing or insufficient tests. This process also checks for story and spec coverage to ensure comprehensive testing across component changes.

Enforcing consistent code reviews for React components in a monorepo involves inspecting changes against established patterns like propTypes and forwardRef. Standardizing the review output with a structured format accelerates PR reviews and helps onboard new contributors.

Yes, the code review process checks for forwardRef and classnames usage in sage-lib. It inspects component changes to enforce these established patterns, ensuring that all React components comply with the required structural conventions before a PR is opened.

Yes, you can request a targeted file review when reviewers ask for changes on a sage-lib component. This allows you to run checks on specific files to verify propTypes, configs.js exports, and Jest tests, delivering actionable feedback for your updates.

A limitation when reviewing React components for pattern compliance is that the checks are specifically tailored to the sage-lib monorepo environment. It focuses on propTypes, forwardRef, classnames, and Jest tests, so it may not apply to other React libraries or custom patterns.