credo-configuration

Configure Credo by creating a .credo.exs file that defines enabled/disabled checks, file inclusion/exclusion patterns, and custom rules. The configuration maps Credo.Check modules to enforce code quality across your lib/, src/, test/, web/, and apps/*/lib/ directories while excluding _build/, deps/, and node_modules/.

Yes. In .credo.exs, enable or disable individual Credo.Check modules and entire categories to match your project's standards. You can configure checks for consistency, readability, design quality, and refactoring opportunities with custom severity levels and exclusions.

Credo configuration scans lib/, src/, test/, web/, and apps/*/lib/ and apps/*/test/ directories by default. It automatically excludes _build/, deps/, and node_modules/ to focus analysis on your project code.

Create a .credo.exs map with name, strict, color, files, plugins, requires, parse_timeout, and an enabled/disabled checks list. Start with core checks and progressively refine rules referencing Credo.Check modules to enforce consistency and readability across your codebase.

Yes. Credo configuration supports umbrella projects by scanning apps/*/lib/ and apps/*/test/ directories. You can define a single .credo.exs at the root to enforce consistent code quality rules across all umbrella applications.

The .credo.exs map includes name, strict mode, color output, file paths, plugins, required dependencies, parse timeout, and enabled/disabled Credo.Check modules. These settings let you tailor static analysis behavior to your project's standards.