Pietro Campagnano

It could be a good idea... Just to understand you better @alessandro-candon which is the problem that made you think "I need to check this DTO/Applier achitecture"? Did you find...

I tried to generate the phar (with `make phar`) but it failed, even on the main branch.. But if I understand correctly the github action make a smoke test on...

> Which error do you get @fain182 ? It's about `/tmp/..` permission, right? the first error is: ``` bin/box.phar compile -c /tmp/arkitect/box.json make: bin/box.phar: Permesso negato make: *** [Makefile:26: phar]...

Interesting, in which situation you found that this was useful to you? :slightly_smiling_face:

It seems a great idea to me :top: To decide the high level goals maybe we could prepare some hypotesis in async and then discuss them in a meeting?

Even if I understand that the redundancy in the name `phparkitect.php` is not beautiful, I think consistency is the key here. We want to surprise the user the least possible...

I suppose that choose just one of the two ways would be better.. So, to understand the best option, why did you find more practical having the results grouped by...

I think that the selection of the classes should be in the "that" clause... so I would think something like: ``` $rule = Rule::allClasses() ->that(new ResideInOneOfTheseNamespaces('App\HappyIsland')) ->andThat(new IsNotOneOf([''App\HappyIsland\Foo''])) ->should(new HaveNameMatching('Happy*'))...

It's not too bad to read, but how would you call in the signature the second argument of the should ? I am trying to see if this solution can...

Maybe we could avoid always to check dependency on PHP built-in classes, using something like this: https://www.php.net/manual/en/reflectionclass.isinternal.php...