Setting up static analyzers is painful, cumbersome, and confusing. First of all, you need to set up one static analyzer per language you use in each editor you use. Static analyzers you love may not be available in your co-worker editors, making code verification in your projects inconsistent. In addition, code quality rules checked in your CI/CD pipelines might be different from the rules in your editor.
Introducing Codiga IDE plugins
We are introducing Codiga IDE plugins, bringing the power of Codiga analysis engine anywhere you write code. The first plugin to be available is IntelliJ and inspect all languages supported by Codiga in IntelliJ products at no cost.
No need to install multiple static analyzers: just one plugin to support all languages. We support the most popular IDEs so the very same rules are being detected on all platforms, making your code verification consistent across all development environments. Finally, the same rules are being used in your CI/CD pipeline so that no error in your IDE = no error in your CI/CD pipeline.
Codiga IntelliJ plugin
The Codiga JetBrains plugin is available on the Jetbrains marketplace. You can install it within IntelliJ, PHP Storm, PyCharm and all other JetBrains products in the plugin section.
Once you install the plugin, add your Codiga API keys in the plugin preferences. You can also associate your Codiga project with your IntelliJ project so that Codiga applies all the preferences of your project in its analysis (max line length, ignored, violations, etc.).
Codiga will then analyze every file you open in your JetBrains product. Analysis results are surfaced within less than three seconds.
If you associate a Codiga project within IntelliJ, you can also select to ignore violations you do not find useful, which will automatically reflect in your project configuration and applies to the analysis done by any contributor of this project, in any development environment.
The Codiga engine can be used within your IDE and check 12+ languages automatically within seconds. Verification is consistent across all IDE and CI/CD pipeline.