By default, your enabled plugins will use a default version (what we refer to as the stable channel). However, in some cases, you may want to specify a different version to match what you’re running locally. (For example, you may be running a newer version of Rubocop than our default version). Previously, this could only be done via a committed .codeclimate.yml or .codeclimate.json file. While that configuration is simple enough (and still necessary to adjust other analysis settings) we recognize it can add a little friction when getting your analysis configuration dialed-in. So we’ve added the ability to select different plugin versions, when available, right from the UI.
Try it out and let us know what you think!
Inspired to configure more? See what you can do with a configuration file by consulting our documentation.
]]>codeclimate-flog
plugin!
The plugin’s ruby_parser
gem was updated to version 3.20.0
, which supports Ruby 3.1 syntax.
If you use Flog and want to run it on Ruby 3.1+ code, be sure to enable either the flog-4-6-6
or beta
channel in your .codeclimate.yml
config file, like so:
plugins:
flog:
enabled: true
channel: flog-4-6-6
Thanks to Fonji on Github for reporting the issue!
]]>One of the key highlights of this release is the migration to the new Manifest V3 format, which introduces a range of benefits and optimizations for our users. With Manifest V3, our extension leverages the latest capabilities provided by Google Chrome, ensuring better performance, security, and overall stability.
Here’s what you can expect from the new version:
Enhanced Performance: The new Manifest V3 format allows us to optimize our extension’s performance, resulting in faster load times and smoother interactions. You’ll notice a more responsive and seamless experience while using our tool.
Improved Security: We have taken advantage of the enhanced security features offered by Manifest V3 to bolster the protection of your browsing experience. Our extension adheres to the latest security standards, keeping your data safe and secure.
Better Stability: We have addressed various stability issues and introduced robust error handling mechanisms to ensure that our extension functions reliably. You can trust that our tool will provide a consistent and uninterrupted experience.
We highly recommend upgrading to the latest version of our browser extension to take full advantage of these improvements. Simply visit the Google Chrome Web Store to update your extension, and you’ll be ready to enjoy the enhanced features and benefits offered by our tool.
We value your feedback and continuously strive to provide the best possible experience. If you encounter any issues or have any suggestions, please reach out to our support team. We appreciate your support as we continue to refine and evolve our browser extension to meet your needs.
Thank you for choosing our tool and being a part of our community.
]]>eslint-7
and eslint-8
have support for the following babel plugins:
eslint-8
now runs ESLint version 8.39.0
.bundler-audit-0-9-1
.golangci-lint
a powerful tool for running linters on your GO codebase.To learn more about each of our plugins, be sure to check out our documentation here: https://docs.codeclimate.com/docs/advanced-configuration#section-plugins
]]>rubocop-1-39-0
or rubocop-1-48-1
channels, you can now use the standardrb rule set when running analysis. To see more about how to turn that on, check that out here Standard Usage Via Rubocop. To learn more about our rubocop
plugin, you can check out our docs here: Rubocopstandard-1-4-0
in either your .codeclimate.yml
or .codeclimate.json
configuration files. To learn more about our standard
plugin, you can check out the page here: Standardsonar-java
to run analysis on your code, you should be able to start using it against your Java 11 code. This behavior will be on by default. If you find that this change negatively impacts your projects, you can use the previous version of sonar-java by setting the channel to sonar-java-4-14
. To learn more about the sonar-java
plugin you can look at our docs here: Sonar Java PluginHere are the channels for each plugin that you can add to either your .codeclimate.yml or .codeclimate.json configuration:
Plugin | New Channel | |
---|---|---|
Brakeman | brakeman-5-4-1 |
Release Notes |
Rubocop | rubocop-1-48-1 |
Release Notes |
ESLint | eslint-8 |
Release Notes |
Reek | reek-6-1-4 |
Release Notes |
Checkstyle | checkstyle-10-7-0 |
Release Notes |
TFLint | stable |
Release Notes |
The CodeClimate Test Reporter tool is highly customizable and supports various programming languages, such as JavaScript, Ruby, Python, and .NET, among others. It works seamlessly with your existing testing infrastructure, allowing you to effortlessly generate comprehensive reports on test coverage. By integrating the tool with your CI/CD environment, you can ensure that your code undergoes thorough testing before deployment to production.
To learn more about configuring CodeClimate to work with your specific testing framework and to get the download links, visit our documentation.
]]>Read more here! And Enjoy!
]]>