Thanks to visit codestin.com
Credit goes to github.com

Skip to content

"FIX_" mode defaults don't match README #6768

@ferrarimarco

Description

@ferrarimarco

Discussed in #6767

Originally posted by david-mcdowell-ilw May 6, 2025
Has anyone noticed this? I believe the README needs to be updated to show all FIX_ variables as false by default.

When running super-linter locally, I don't see any fixes applied and still see warnings for Markdown formatting, for example.

When I pass the flag explicitly in my super-linter.env file, it resolves the error and applies changes to the file:

FIX_MARKDOWN_PRETTIER=true

@ferrarimarco if it helps, it seems the defaults in the README.md were changed on this PR:
#6028

I think these are all the FIX_ settings currently marked as true in the README.md. I assume they all have the same mismatch.

  • FIX_CSS_PRETTIER
  • FIX_DOTNET_SLN_FORMAT_WHITESPACE
  • FIX_GRAPHQL_PRETTIER
  • FIX_HTML_PRETTIER
  • FIX_JSON_PRETTIER
  • FIX_JSONC_PRETTIER
  • FIX_JSX_PRETTIER
  • FIX_MARKDOWN_PRETTIER
  • FIX_TYPESCRIPT_PRETTIER
  • FIX_VUE_PRETTIER
  • FIX_YAML_PRETTIER

Metadata

Metadata

Assignees

No one assigned

    Labels

    O: backlog 🤖Backlog, stale ignores this labelbugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions