when working on customer projects i usually have several packages under the src directory.
customer.theme, customer.site, and several collective.* and Products.* packages i need to extend/adapt.
before touching these packages, one should run code-analysis and fix errors - if any.
to not get overwhelmed by errors of all the other packages currently in src/ folder on currently needs to define a separate part for code analysis for this package:
it would be a nice feature to allow to limit the directory given in the buildout part further via a command line argument
bin/code-analyisis -d some.package or bin/code-analysis -d src/some.package
currently this recipe only allows to define the directory to check via an option in the buildout configuration:
when working on customer projects i usually have several packages under the src directory. customer.theme, customer.site, and several collective.* and Products.* packages i need to extend/adapt. before touching these packages, one should run code-analysis and fix errors - if any. to not get overwhelmed by errors of all the other packages currently in src/ folder on currently needs to define a separate part for code analysis for this package:
it would be a nice feature to allow to limit the directory given in the buildout part further via a command line argument
bin/code-analyisis -d some.package
orbin/code-analysis -d src/some.package