Prospector on Visual Studio Code

Visual Studio Code plug -in: Prospector code quality check tool

In order to improve the integration of Prospector and mainstream IDE, I developed a Visual Studio Code plug -in based on the VS Code Linter plug -in. Although the plug -in is not currently maintained, it provides valuable experience for the rapid construction of a new Prospector VS Code integrated plug -in.

This plug -in allows users to run the Prospector directly in VS Code, and check the code check results in the editor to use the experience smooth and seamless.

Results display:

Plug -in has been published in the Visual Studio Code market.

Provector Introduction

Provector is a powerful Python code static analysis tool collection. It improves the quality of code by running multiple code checkers and static analysis tools at one time. It integrates many commonly used tools and can easily configure and customize the needs of different projects. You can view the complete list of supporting tools.

In the years of working in CAMPTOCAMP, we have made many improvements to the Prospector, including:

Python 3.12 Compatibility

: Make sure that the Prospector is perfectly compatible with the latest version of Python.
• Integrate RUFF : Integrate RUFF, a fast Python code checker to improve the inspection performance.
• Improve BANDIT and Mypy Integration : Enhanced the integration of Bandit (safety -related static analysis tools) and Mypy (static type checking tool).

Support the configuration file in the pypi package

• : Allows users to publish the Prospector configuration file as a PYPI package. Fixed
: Fix a variety of problems so that the tool is more reliable.
• The latest Prospector version
• In the latest version of Prospector, I focus on improving the integration of and IDE, especially the JSON output generated by the Prospector. These improvements enable Prospector to better interact with code editor and IDE (such as Visual Studio Code):
The end of the line number and characters

: This change allows the IDE to highlight the code element (such as, function or variables) that have problems with the entire problem, not just the first character. This provides a more intuitive user experience when checking the code check errors.

Document URL

: New features, provide direct links to related documents for each code checking rule. This allows developers to quickly understand and solve problems without the need to search for documents manually.

• Other useful related packages I maintain
Basic Prospector configuration file
• : A set of basic configuration files to help you configure the Prospector for the project. The PROSPECTOR configuration file used to avoid repeated messages
: A set of configuration files designed to prevent duplicate code checking messages, making the output more concise and easy to understand.

The above is the detailed content of Prospector on Visual Studio Code. For more information, please follow other related articles on the PHP Chinese website!