Skip to content

Allow aliased standards via symlinks. #29

Merged
merged 1 commit into from May 13, 2012

2 participants

@ktomk
ktomk commented May 12, 2012

I wanted to replace a standard that I had installed with/in pear with a development version from github that was in another directory. So I symlinked the standard directory to the development directory:

.../Standards/Symfony2  ->  ~/Developing/Symfony2-coding-standard

This needed the requested changes.

@ktomk
ktomk commented May 12, 2012

X-Ref: https://pear.php.net/bugs/bug.php?id=19417 - Configuration via symlinks is useful where you have a shared configuration and/or IDE integrations that do not allow to specify standard-paths (e.g. Phpstorm).

@gsherwood gsherwood merged commit 5de1faa into squizlabs:master May 13, 2012
@gsherwood
Squiz Labs member

Thanks for another great patch.

@ktomk ktomk referenced this pull request May 14, 2012
Merged

Tests for symlinked standards #32

@gsherwood gsherwood added a commit that referenced this pull request Jun 19, 2012
@gsherwood gsherwood Fixed bug #19448 : Problem with detecting remote standards. Note that…
… this reverts the changes from pull request #29, although the symlink issue that code was fixing appears to have now been fixed by other changes to CodeSniffer.php anyway.
fbab82e
@yuzuemon yuzuemon pushed a commit that referenced this pull request Aug 19, 2014
@gsherwood gsherwood Fixed bug #19448 : Problem with detecting remote standards. Note that…
… this reverts the changes from pull request #29, although the symlink issue that code was fixing appears to have now been fixed by other changes to CodeSniffer.php anyway.
e4c9eac
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.