Search Results for "or-tools"

...Ruff can be configured through a pyproject.toml, ruff.toml, or .ruff.toml file (see: Configuration, or Settings for a complete list of all configuration options). Ruff supports over 500 lint rules, many of which are inspired by popular tools like Flake8, isort, pyupgrade, and others. Regardless of the rule's origin, Ruff re-implements every rule in Rust as a first-party feature.

...It provides real-time linting and formatting feedback as developers write code, helping catch errors, enforce style guidelines, and automatically fix issues where possible. The extension is built on top of Ruff’s high-performance Rust-based engine, which is significantly faster than traditional Python linting tools, allowing near-instant feedback even on large codebases. It supports both linting and formatting workflows, consolidating the functionality of multiple tools such as Flake8, Black, and isort into a single unified interface.

Ansible Lint is a command-line tool for linting playbooks, roles and collections aimed towards any Ansible users. Its main goal is to promote proven practices, patterns and behaviors while avoiding common pitfalls that can easily lead to bugs or make code harder to maintain. Ansible lint is also supposed to help users upgrade their code to work with newer versions of Ansible. Due to this reason we recommend using it with the newest version of Ansible, even if the version used in production...

JavaScript Lint is a development tool that validates JavaScript code for best coding practices, finding common mistakes without actually running the script or opening the web page.

PyChecker is a static analysis tool for finding bugs in Python source code. It finds problems that are typically caught by a compiler for less dynamic languages, like C and C++. It is similar to lint.

cpplint is a free lint for C++. It checks C++ code looking for hard to see errors while also making comments on the code's style.

JCSC is a highly configurable checking tool for your Java source code. It checks the compliance to a defineable coding standard like naming conventions and code structure. Also signs of bad coding, potential bugs are found. JCSC is inspired by lint.