Back to all reviewers

Follow established conventions

helix-editor/helix
Based on 5 comments
Toml

Configuration settings should align with official language documentation and established community standards rather than arbitrary personal preferences. This applies to indentation styles, formatter configurations, and syntax requirements.

Code Style Toml

Reviewer Prompt

Configuration settings should align with official language documentation and established community standards rather than arbitrary personal preferences. This applies to indentation styles, formatter configurations, and syntax requirements.

For language-specific settings, consult official documentation:

  • Use 2 spaces for Typst indentation as specified in official docs, not 4
  • Follow PEP 8 for Python when setting required indentation
  • Only enable auto-format when it’s standard practice for the language

For tool configurations, ensure commands and arguments are syntactically correct:

# Correct formatter configurations
formatter = { command = "prettier", args = ["--parser", "typescript"] }
formatter = { command = "biome", args = ["format", "--stdin-file-path=a.js"] }
formatter = { command = "deno", args = ["fmt", "--ext", "js"] }

# Use full 6-character hex codes, not 3-character shortcuts
"ui.background" = { bg = "#262335" }  # not "#263"

This ensures consistency with ecosystem expectations and prevents configuration errors that could break functionality.

5
Comments Analyzed
Toml
Primary Language
Code Style
Category

Source Discussions