Repository navigation
Install StructArmed #22
Description
Activity
that should work, but will may need to pass update config for "Source" layer, as everything is layer:
->layer("Source", [ __DIR__ . '/../../src', __DIR__ . '/../../test', __DIR__ . '/../../composer.json' ])
or probably manual via paths:
vendor/bin/structarmed analyze ../src ../test ../composer.json
@gsteel Do you have example project directory? I may need to have example structure project directory to test locally tho ...
Sure - Laminas i18n has a load of tools installed separately:
https://github.com/laminas/laminas-i18n/tree/3.1.x/tools
I've used
/tools/as standard location on quite a lot of projects to reduce dependency conflicts. Renovate keeps things up-to-date nicely too.@gsteel it seems can't fully working with directory jump parent, as composer.json is not in the root:
➜ vendor/bin/structarmed analyze ../../src ../../test ../../composer.json Error: path [../../composer.json] is not analysable. Expected a directory, a .php file, or the project composer.json.
also, the layer definiton can define by relative directory:
->layer('Config', 'src/ConfigProvider.php')
The solution I can think of is add ability to setup base path via command line, eg:
vendor/bin/structarmed analyze --basepath=../../
so base path will be new root.
I can work on feature for 0.19.0 :)
Reacted by George Steel@gsteel I am working on the new
StructArmedfeature to allow define--basepath=../../:I've released StructArmed 0.19.0 with add ability to setup basepath via
--basepath/-din CLI https://github.com/boundwize/structarmed/releases/tag/0.19.0Reacted by George Steel
Add a make target to install StructArmed by @samsonasik
It should:
Questions for @samsonasik
Can we install it to
/tools/structarmedinstead of in require-dev of the project?