-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scan depth as parameter #45
Comments
Potherca
added a commit
that referenced
this issue
Feb 1, 2018
Potherca
added a commit
that referenced
this issue
Feb 1, 2018
Thank you for taking the time to report this, my apologies for the slow response (we try to respond within a week). I have opened a pull-request implemented this, if @frenck agrees with the implementation, I am not opposed to adding this feature. |
Potherca
added a commit
that referenced
this issue
Feb 1, 2018
@frenck Ping? |
frenck
pushed a commit
that referenced
this issue
Oct 25, 2018
frenck
pushed a commit
that referenced
this issue
Oct 25, 2018
* Adds the ability to set the max depth from the composer.json file Fixes #45 * 📚 Adds method descriptions to code docs * 🚜 Tweaks getMinDepth * 🚜 Reduces amount of logic * 🚜 Change error message const name for consistency * 📚 Adds documentation for search depth customization * 🚜 Renames extra option to phpcodesniffer-search-depth * 🚑 Fixes default search depth (which was actually 3, not 4) * 🚑 Corrected PHP doc return type
This feature has been added @alexdesignworks, thanks to @Potherca! Will be part of the next release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem/Motivation
This is feature request.
Current scan depth is set to less then 4. This may not work for cases when
ruleset.xml
is provided in the package that contains multiple rulesets - such package would use additional parent directory to hold multiple rulesets.Exposing scan depth to be extracted from
extra
section would allow more granular per-project config.The text was updated successfully, but these errors were encountered: