aphiria VS framework

Aphiria: https://www.aphiria.com/

I’ve been wanting a project just like this so I can finally try Aphiria! Very well done project, definitely worth a look.

Aphiria is a fav of mine - lesser know but being a fresh take since PHP 8 it has some opportunities that older frameworks never did.

I haven't promoted it much because it's still in alpha testing, but my framework Aphiria.

Compare output from Laravel to a framework that's not bed-ridden with overuse of Reflection, like Aphiria and see the result for yourself.

One of the promising frameworks I noticed is https://www.aphiria.com/ in case someone is interested to try out something different, something that's not full of evangelists who are wolves in sheep clothing.

Those are some of the things I sought to solve with MixerAPI. This is another project which saw the same shortcomings as I did, https://www.aphiria.com/, I just didn't think it made sense to build a ground-up framework to solve the problem. Use something existing, build on top, and don't mess with existing workflows in the framework. Just augment them is how I feel about things at least.

Author of Aphiria here. The base controller just provides a few properties and helper methods. If that's too much coupling for you, it supports POPOs as controllers too.

I use them as a micro-optimization in my router. Whenever I find a potential matching route, I yield return it and check it against constraints, eg does the HTTP verb match. This way, I don't have to grab all potential route matches prior to checking constraints.

In April of 2021, version 1.0 of FEAST Framework was released. One year ago, version 2.0 of FEAST Framework was released. Today, I am happy to announce the release of version 3.0 of FEAST Framework.

I would like to submit https://github.com/feastframework/framework to this. It's a small framework I wrote and what I think sets it apart is it has 100% code coverage with PHPUnit and has 100% static type analysis with psalm.

FEAST Framework. Go figure.

This isn't quiiiite the same as your scenario, but in December the (not yet at that time) version of FEAST Framework didn't have a single unit test outside of one simple class (The Date class). By March, it had 100% coverage.

You can find it here: FEAST Framework

I have minor issues with the PSR-11 interface due to it not being capable of strong typing on the variables... And yet my framework (https://github.com/feastframework/framework) uses it. It's nice to have that layer of flexibility. Admittedly, I pissed a few people off by just throwing the interface in my codebase but whatevs 😂

This book actually had a very large hand in the development of my PHP Framework FEAST and definitely is one of the books that inspired my goal (which was achieved) of 100% code coverage.