wheels analyze code

Analyzes code quality in your Wheels application, checking for best practices, potential issues, and code standards compliance.

Usage

wheels analyze code [path] [--fix] [--format=<format>] [--severity=<severity>] [--report]

Parameters

  • path - (Optional) Path to analyze. Default: current directory (.)

  • --fix - (Optional) Attempt to fix issues automatically

  • --format - (Optional) Output format: console, json, junit. Default: console

  • --severity - (Optional) Minimum severity level: info, warning, error. Default: warning

  • --report - (Optional) Generate HTML report

Description

The analyze code command performs comprehensive code quality analysis on your Wheels application. It checks for:

  • Code complexity and maintainability

  • Adherence to Wheels coding standards

  • Potential bugs and code smells

  • Duplicate code detection

  • Function length and complexity metrics

  • Variable naming conventions

  • Deprecated function usage

Examples

Basic code analysis

wheels analyze code

Analyze specific directory

wheels analyze code app/controllers

Auto-fix issues

wheels analyze code --fix

Generate HTML report

wheels analyze code --report

Analyze with JSON output for CI/CD

wheels analyze code --format=json

Check only errors (skip warnings)

wheels analyze code --severity=error

Analyze and fix specific path with report

wheels analyze code app/models --fix --report

Output

The command provides detailed feedback including:

  • Complexity Score: Cyclomatic complexity for functions

  • Code Standards: Violations of Wheels conventions

  • Duplicate Code: Similar code blocks that could be refactored

  • Suggestions: Recommendations for improvement

  • Metrics Summary: Overall code health indicators

Notes

  • Large codebases may take several minutes to analyze

  • The --fix flag will automatically fix issues where possible

  • HTML reports are saved to the reports/ directory with timestamps

  • Integration with CI/CD pipelines is supported via JSON and JUnit output formats

  • Use .wheelscheck config file for custom rules and configurations

Last updated

Was this helpful?