wp-graphql / wp-graphql/wpgraphql-acf

Suggestion: Recommend `phpsab` for VSCode

Open
#52 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: actionable type: enhancement
Dominant language
PHP
Stars
110
Forks
18
PR merge metrics
No merged PRs in 30d

Description

What problem does this address?

Both ikappas.phpcs and persoderlind.vscode-phpcbf have been abandonded since 2018 and have many known issues with VSCode itself and even more on non Mac devices.

Additionally, why install 2 plugins when one will suffice?

What is your proposed solution?

I recommend ValeryanM.vscode-phpsab, which is the successor of the currently mentioned plugins.

A .vscode/settings.json config can even be included in the repo:

{
	"phpsab.executablePathCBF": "vendor/bin/phpcbf",
	"phpsab.executablePathCS": "vendor/bin/phpcs"
}
What alternatives have you considered?

No response

Additional Context

https://tommcfarlin.com/php-sniffer-for-visual-studio-code/

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect the repository's current VSCode and PHP CodeSniffer plugin references, then compare them with the proposed .vscode/settings.json configuration and the phpsab extension. Done means the abandoned plugin recommendations are replaced and the suggested phpsab executable paths are included where appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, vscode
Domain
tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.