https://bugs.kde.org/show_bug.cgi?id=397885
Bug ID: 397885
Summary: clazy-standalone: option to exclude subdirs
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
Given a software project which has (for whatever reason) some copies of
3rd-party code in some subdirs. Such 3rd-party code copies often should stay
untouched from optimizations, to keep the diff to the original code as small as
possible.
So it would be useful to be able to exclude those subdirs from clazy runs, to
both not spend time on code which should not be changed as well as keep the
result lists clean from uninteresting results (and fixes).
Possibly could be done by adding a new comand line flag (--ignore-dirs= or with
a better name) which would take a list of either absolute paths or subdir name
patterns/wildcards.
Another option would be config files (.clazy?) to control that behaviour
Being able to overrule any config files via the command line though would be
good to have, e.g. when running clazy from a UI program or some tooling with a
separate config system.
Example:
KDevelop codebase which has some copies of subversion code, astyle code and
qtcreator's qml parsing code. Those copies are in their own special
subdirectories (all named 3rdparty/) and should be often ignored when running
clazy-standalone on the whole project, like with performance checks.
So something like
clazy-standalone --ignore-dirs=3rdparty -p /path/to/kdevelop/builddir
/path/to/kdevelop/sources -checks=check1,check2
would improve user experience.
--
You are receiving this mail because:
You are watching all bug changes.
