Download the PHP package obliviousharmony/vscode-phpcs-integration without Composer

On this page you can find all versions of the php package obliviousharmony/vscode-phpcs-integration. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of obliviousharmony/vscode-phpcs-integration

Informations about the package vscode-phpcs-integration

VS Code PHP_CodeSniffer Extension

Integrates PHP_CodeSniffer into VS Code.

This extension uses the version of PHPCS defined by the platform-specific executable setting. Through the use of custom reports we are able to generate diagnostics, code actions, and document formatting that fully utilizes VS Code's available features.

Configuration

Until you configure it, this extension will not lint any files.

Standard (phpCodeSniffer.standard)

This dropdown selects the coding standard that will be used. There are a few options that, when selected, will instead change the behavior of the extension.

Disabled

This option will prevent the extension from linting any documents.

Default

Allow PHPCS to decide what standard should apply to the document. It will either use the default standard if one is configured, otherwise, it will try to find one in the workspace root and all parent directories.

Automatic

When selected, this option will cause the extension to search for an applicable coding standard file (.phpcs.xml, phpcs.xml, .phpcs.xml.dist, phpcs.xml.dist). The extension starts in the document's folder and traverses through parent directories until it reaches the workspace root. If the extension fails to find a file it will do nothing and output an error.

Custom

This option will use the content of the phpCodeSniffer.standardCustom input as the standard. This can be the name of a custom ruleset, or, a path to a custom standard file. If a relative path is given it will be based on the workspace root that the document resides in (untitled documents use the first root).

Executable (phpCodeSniffer.exec.linux, phpCodeSniffer.exec.osx, and phpCodeSniffer.exec.windows)

This text input allows for setting a path to a platform-specific PHPCS executable. If a relative path is given it will be based on the workspace root that the document resides in (untitled documents use the first root). Any arguments or options added after the executable will be passed to it automatically.

You may also set the phpCodeSniffer.autoExecutable option if you'd like for the extension to automatically search for an executable. This works by looking for a {vendor-dir}/bin/phpcs ({vendor-dir}\bin\phpcs.bat on Windows) file in the document's directory and then traversing up to the workspace folder if it does not find one. When it fails to find one automatically it will fall back to the explicit option.

File and Folder Exclusions (phpCodeSniffer.exclude)

This array of glob patterns allows you to exclude files and folders from linting. While the extension does respect any file rules in your coding standard, this option allows you to define additional rules.

Autofix on Save

Rather than providing an option here, this extension encourages you to use the built-in VS Code editor.formatOnSave option:

Using in Containerized Development Environments (phpCodeSniffer.autoloadPHPCSIntegration)

If you are using a container for your development environment we would strongly recommend using one of VS Code's remote development extensions. However, if this is not possible, we have provided a Composer package with the files required to integrate with PHPCS. You must install these files alongside PHPCS (globally or per-project) in order for the extension to work properly. Once you have installed the package it will be used instead of the build-in integration when phpCodeSniffer.autoloadPHPCSIntegration is enabled.

All versions of vscode-phpcs-integration with dependencies

PHP Build Version
Package Version
No informations.
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package obliviousharmony/vscode-phpcs-integration contains the following files

Loading the files please wait ....