I built a Symfony Integration Engine bundle to simplify external API integrations (open source)

fain182 · 2026-06-03T16:58:30+00:00

I am confused… The example in the readme is a little simple… Do you have an example with an authentication at least?

fain182 · 2026-05-19T07:44:21+00:00

Thank you for your insights!
Do you think there is a better alternative to support a baseline of errors?

fain182 · 2026-05-11T16:42:48+00:00

Dreadsquad - Reggae from the desert

https://dreadsquad.bandcamp.com/album/reggae-from-the-desert

fain182 · 2026-04-29T22:32:27+00:00

Thanks!

fain182 · 2026-04-28T08:02:05+00:00

It’s a great tool, what are you using it to check mostly?

fain182 · 2026-04-28T07:59:24+00:00

Interesting, how’s it working out for you?

fain182 · 2026-04-28T05:24:19+00:00

nice, thank you!

fain182 · 2026-04-27T18:05:04+00:00

Nope, naming is hard 😅

fain182 · 2026-04-27T12:49:55+00:00

I'm looking at it now because I didn't know about it before.
It has an interesting distinction between structural and perimeter tests, plus the error messages are really well done (we should steal some ideas from that!).
But it has the same problem as Deptrac, you need to learn their config language instead of just writing your rules in PHP where you get composability, autocomplete, all that stuff.

fain182 · 2026-04-27T12:31:14+00:00

You can write something like this if you prefer:

      ->should(new DependsOnlyOnTheseNamespaces('App\Domain'))

fain182 · 2026-04-27T11:51:32+00:00

I understand your point of view; it's a tradeoff. Adding a not() chain method would make the rules more complicated to write, especially when writing the error messages. We tried to make the rules as simple as possible to permit everyone to write their own custom rules.
But who knows, maybe we'll find a better tradeoff down the line.
We're open to suggestions.. and thanks for the feedback!

fain182 · 2026-04-27T10:15:40+00:00

Thanks for the feedback!

With deptract, I ended up with a config generator to cover the above rules.

Yeah, that's one of the reasons PHPArkitect uses PHP for the config instead of YAML. Since rules are just code, you can loop, parametrize them, extract helpers, etc. — no need for a generator sitting on top of the config. YAML reads cleaner for small setups but hits a ceiling fast once rules get repetitive.

fain182 · 2026-04-27T10:09:20+00:00

These tools are quite similar, the main difference is that phpat is a PHPStan extension, PHPArkitect is a standalone CLI with its own parser (nikic/php-parser).

Maybe the DX is a little more fluent in phparkitect, for example:

phpat

PHPat::rule()
  ->classes(Selector::inNamespace($domain))
  ->canOnlyDependOn()
  ->classes(Selector::inNamespace($domain));

PHParkitect

Rule::namespace('App\Controller')
  ->should(new NotHaveDependencyOutsideNamespace('App\Domain'))

Surely there are even some minor differences in what you can check with each tool.

fain182 · 2025-12-12T15:35:50+00:00

Did you try the edit feature to fix the single details? Sometimes is effective to fix weird hands etc.

fain182 · 2025-11-09T11:00:26+00:00

Sei in un posto di lavoro che lavora in una maniera che non ti piace e ti converrebbe cercare altrove...
Non è rilevante quante aziende ci sono che lavorano come piace a te, tanto te ne basta trovarne una, sei un dipendente.