You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 18, 2024. It is now read-only.
We can extend and replace the present request/response with the above class. I'm still open to opinions on various other approaches used in slim and other micro frameworks.
The text was updated successfully, but these errors were encountered:
I would like to try (first) use Gleez Autoloader in Codebench and if it will show their best side to use it everywhere. Including for Request/Response, etc.
But I would like to express my opinion about Request/Response. You understand that this is a large amount of work? Let us first transform our classes to namespaces. Let's create a new branch for this. Current feature-bootstrap-3 branch can be a master. Current master may be old-stable. New version we can bump to 1.0.0
I believe that in order so that we could use all sorts of things from Symphony (Zend, Laravel, Fuel, Yii, Aura, Nette, Ohanzee, etc,) we must use PSR-0/1/2/3/4
IMHO we should replace the existing request/response with the symfony httpfoundation.
https://github.com/symfony/symfony/tree/master/src/Symfony/Component/HttpFoundation
We can extend and replace the present request/response with the above class. I'm still open to opinions on various other approaches used in slim and other micro frameworks.
The text was updated successfully, but these errors were encountered: