Skip to main content

Ideas

🚧 Do you want to request a feature? Please review the list below and open an issue.

Inspiration#

Here are tools that this linter could learn from. Suggestions welcome.

Linting rules#

Accessibility checks#

HTML validation#

Developer tools#

Research#

Python developer tools#

Most of curlylint’s CLI is already based on that of black: include/excludes, config file, error, success, verbose output. It would be nice to learn from flake8’s plugin system, eventually.

CLI ideas#

  • Support configuration from setup.cfg.
  • Support configuration from .editorconfig.
  • Support using a file with ignore paths.
  • Disable colored output.
  • Cache results / only check changed files.

Linting ideas#

  • Support disabling rules via code comments.

Rules ideas#

Wishlist#

Code smells#

HTML5#

Accessibility#

ARIA#

Security#

Template languages#

  • Forbid specified template language syntax.
Django#
  • {% if foo %}{{ foo }}{% else %}bar{% endif %} => {{ foo|default:"bar" }}
  • {% with foo as bar %} ... [ not using {{ bar }} ] ... {% endwith %}
  • {% endblock %} vs. {% endblock blockname %}
  • Forbid marking variables as "safe"

Code style#

Rejected ideas#

Formatting#

See https://github.com/prettier/prettier/issues/5944#issuecomment-549805364. I’m much more interested in having automated formatting with a Prettier plugin, than adding formatting rules to a linter.