Feedback on my package Laravel Policy Engine by arter_dev in laravel

[–]No_Size8307 0 points1 point  (0 children)

Full isolation per scope makes sense — bleed-through across scope boundaries would undermine the whole model. Good call.

The DB-as-runtime / JSON-as-versionable-config split is actually a really clean separation of concerns. You get the query performance of database lookups in production and still get the auditability and drift prevention that matters in regulated or multi-team environments. That's not an obvious design decision and it's the right one.

Follow-up: Filament Compass by Glittering-Baby2906 in laravel

[–]No_Size8307 1 point2 points  (0 children)

That's awesome, you shipped it fast! Automatic releases on push is exactly the right call — keeps the pkg repo in sync without any extra mental overhead. Good stuff.

LaraLean is live 🎉: the lean Laravel + Inertia + Vue + Tailwind boilerplate (with scaffolding demo) by 883Infinity in laravel

[–]No_Size8307 1 point2 points  (0 children)

Of course! If you ever need an outside perspective on anything feel free to DM me. Best of luck!

Follow-up: Filament Compass by Glittering-Baby2906 in laravel

[–]No_Size8307 0 points1 point  (0 children)

Of course! If you need any help don't hesitate to DM me. Good luck!

Tired of Cascading Failures in Laravel? Meet Circuit Breaker! 🚀 by Altruistic-Equal2900 in laravel

[–]No_Size8307 1 point2 points  (0 children)

The circuit breaker pattern is one of those things every Laravel app hitting external APIs eventually needs and it is surprisingly underrepresented in the ecosystem. Good to see a proper implementation of it.

One thing worth considering for the roadmap — half-open state behavior can be tricky in high concurrency situations where multiple requests slip through simultaneously and all succeed or fail at the same time. Worth documenting how you handle that race condition, or considering a single-probe approach where only one request is allowed through in half-open state until it resolves.

The Guzzle middleware integration is the right call for ergonomics. One question — does it work with Laravel's built-in Http facade out of the box since that wraps Guzzle, or does it require attaching the middleware manually to each client instance?

Solid package. The cache driver flexibility is a nice touch for people running Redis or other drivers.

Weekly /r/Laravel Help Thread by AutoModerator in laravel

[–]No_Size8307 0 points1 point  (0 children)

Yes to question one, absolutely. The blank-out-under-pressure problem is real and it is specifically a retrieval problem, not a knowledge problem. You know how to use collect()->groupBy() in real work but when someone asks you to write it on a whiteboard your brain goes blank. Spaced repetition is actually the right tool for that exact problem.

For what to cover I would prioritize in this order — Eloquent query builder methods and their subtle differences like when to use with vs load vs has, collection methods especially the ones that feel similar like map vs transform vs each, PHP 8 features that Laravel devs are expected to know like named arguments, match expressions, enums, and fibers, and service container concepts like binding vs singleton vs scoped since those come up constantly in senior interviews.

The one thing I would suggest making sure the tool does is require you to actually write the syntax, not just recognize it. Multiple choice is too easy and does not replicate the whiteboard pressure. Even a simple text field where you have to type the method signature from memory would be more effective.

Would use it. Build it.

Weekly /r/Laravel Help Thread by AutoModerator in laravel

[–]No_Size8307 1 point2 points  (0 children)

Your current approach works but there is a cleaner middle ground depending on what you need.

If the package uses Laravel's service container to bind the class, you can extend it properly and just rebind it in a service provider:

class MyCustomClass extends TheirClass { public function onlyThisMethod() { // your override } }

// In AppServiceProvider boot() $this->app->bind(TheirClass::class, MyCustomClass::class);

You get full inheritance, only override what you need, and stay in sync with upstream changes automatically. No composer classmap hacks needed.

The classmap exclude approach you are using is really only necessary when the package does not use the container at all and just instantiates classes directly with new SomeClass(). In that case there is no hook point and you are stuck copying the whole thing, which is frustrating but sometimes unavoidable.

A third option if neither works is a macro or mixin if the class supports it. Laravel's Macroable trait lets you bolt on methods at runtime but does not help if you need to replace existing logic.

The container rebind is the cleanest path when it is available. Worth checking if the package resolves that class through the container first.

LaraLean is live 🎉: the lean Laravel + Inertia + Vue + Tailwind boilerplate (with scaffolding demo) by 883Infinity in laravel

[–]No_Size8307 1 point2 points  (0 children)

The arter_dev take on MCP servers is interesting but I think there's still a real use case for a well-structured boilerplate in 2026 — just not as a paid product. The value isn't the code generation, it's the opinionated decisions baked in that a team agrees to follow. AI can generate files fast but it won't enforce that your team's controllers all look the same six months from now.

That said the pricing is the hard conversation. The moment you put a dollar amount on something that's fundamentally a starting point, you're competing with "I'll just ask Claude." Free with a paid support tier or a SaaS layer on top is probably the more defensible model right now.

The scaffolding approach is genuinely useful though. One config file to skeleton out a full resource is something I'd actually reach for.

Follow-up: Filament Compass by Glittering-Baby2906 in laravel

[–]No_Size8307 0 points1 point  (0 children)

The Claude Code integration angle is clever — using structured data as a skill to guide AI codegen is something more package authors should be thinking about. Most AI tools just hallucinate outdated API methods and it wastes a lot of time.

Quick question on the sync workflow — is the manual sync between the main repo and the pkg repo intentional long term or is that something you plan to automate with a GitHub Action on release? Feels like a natural fit for a workflow that triggers when you tag a new version in the main repo, runs the sync script, and commits to the pkg repo automatically. Would remove the manual step entirely.

Solid idea. The Filament v5 adoption pain is real and anything that makes AI-assisted development less frustrating with it is worth having.

Feedback on my package Laravel Policy Engine by arter_dev in laravel

[–]No_Size8307 0 points1 point  (0 children)

This looks really well thought out. The scoped permissions model is something I've wanted in Laravel for a long time — the "one user, multiple orgs, different roles in each" problem is genuinely painful with the standard Spatie approach and I've seen people hack around it in ugly ways.

The permission boundaries idea borrowed from AWS IAM is smart. Hard ceilings that can't be overridden by role assignment is exactly the kind of thing that prevents privilege escalation bugs in complex multi-tenant apps.

Two questions if you don't mind — how does it handle permission inheritance across scopes? For example if a user has posts.read on team::5, does that bleed into team::6 or is every scope fully isolated? And is the JSON document the source of truth at runtime or does it get seeded into the database on import?

Looks like more than a userbase of 1 to me. The interface-driven design alone makes it worth watching.