rm-hull / chakra-error-fallback / 19805179568

92%

push

github

chore: Configure and apply Prettier (#48)

* fix: Handle cyclic error causes gracefully

The `Cause` component now uses a `seen` set to track errors it has
already processed. This prevents the component from entering an
infinite rendering loop when error objects form a cycle via the
`error.cause` property.

A test case and a Storybook story were added to verify the behavior.

* fix: Initialize Set defensively in Cause

Ensure that the `seen` prop passed to the `Cause` component
is always iterable when constructing `nextSeen`. If `seen` is
nullish, an empty array (`[]`) is used instead to prevent
potential runtime errors.

* test: Use render function for cyclic errors story

The setup for the cyclic error objects (`errorA`, `errorB`) is moved
from the module scope into the story's `render` function.

This ensures that a fresh error object cycle is created on every
render, which prevents potential state leakage or caching issues
within Storybook. The `cause` is set using `defineProperty`.

* chore: Configure and apply Prettier

Integrate Prettier into the development dependencies and workflow
to enforce consistent code styling.

This commit includes:
*   Installation of `prettier` and related ESLint plugins.
*   Addition of the `format` script to `package.json`.
*   Application of automated formatting across the codebase.

* chore: Configure advanced flat ESLint setup

The ESLint configuration has been comprehensively updated to leverage a
flat configuration structure, integrating several new essential
plugins for strict code quality enforcement.

This update introduces rules for:

*   Import resolution and syntax validation (`eslint-plugin-import`).
*   Promise usage best practices (`eslint-plugin-promise`).
*   React Compiler requirements (`eslint-plugin-react-compiler`).
*   Detection of unused imports (`eslint-plugin-unused-imports`).
*   Mandatory TypeScript type-checked rules.

The configuration also ensures compatibility with Prettier via
`eslint... (continued)

27 of 31 branches covered (87.1%)

Branch coverage included in aggregate %.

4 of 4 new or added lines in 2 files covered. (100.0%)

59 of 62 relevant lines covered (95.16%)

5.98 hits per line