Home

Roadmap

Rules

• Duplicated method
• Unneeded private method
• Unnecessary if-else/return true/false
• Rules for checking specs
• Security checks #79
• Raise in finalize
• ...

Changes / additions / improvements

• Autocorrect issues #34
• Semantic analysis
• Built-in watcher
• Rule property to filter by filetypes/wildcards
• Ameba extensions
• Website (better documentation + blog)
• ...

Integrations

• Emacs — ameba.el
• SublimeText — SublimeLinter-contrib-ameba
• Atom
• VSCode extension — vscode-crystal-ameba
• Vim
  • vim-crystal via Syntastic
  • via Ale
• Codacy — codacy-ameba
• pronto

Extensions

Would be really cool to make ameba more extensible. Let's say if someone would need the linting of config/*.yml or *.ecr files, he would just create a third-party project, register its own "rules" through Ameba's interface and use it together with the main "engine".

So the runner/formatters/config etc. will remain the same and the developer will need to take care of his own "rules".