[Repo Assist] docs: document configSearch setting and standard variable substitution#95
Draft
github-actions[bot] wants to merge 1 commit intomasterfrom
Draft
Conversation
- Add phpcbf.configSearch to the Extension Settings list with a clear description of its auto-discovery behaviour - Update phpcbf.configSearch entry in the default-settings JSON block - Expand the phpcbf.standard entry to show , , and ~/... are supported in the path Closes #17 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 This is an automated draft PR from Repo Assist, an AI assistant.
Summary
The
phpcbf.configSearchsetting has been present inpackage.jsonand the extension code since v0.0.9 but was never documented in the README. Users who need automatic phpcs.xml discovery have had to discover this feature by accident.This PR:
phpcbf.configSearchto the Extension Settings list with a description of what it does and when to use itphpcbf.configSearch: falseto the default settings JSON blockphpcbf.standardentry to show that\$\{workspaceFolder},\$\{workspaceRoot}, and~/...paths are supported (this was added in v0.0.9 but not reflected in the README)Motivation
Issues #7 and #17 both arise from users not knowing about these features:
standardwhen\$\{workspaceFolder}would work portablyconfigSearchexists and can auto-locate theirphpcs.xmlTest Status
Documentation-only change. All 7 unit tests pass (
npm run test:unit).