spiral / framework Goto Github PK

I should find nice and clean way to add commands to react controllers, models (orm and odm) and views (?) as it already implement for migrations. Trick is to have additional config to declare default namespace, base directory and etc. Additionally, to think about custom controller templates.

Code generation will be done using Reactor classes not stubs.

What is middleware and what is service. Keep syntax nice and clean. Think about Route based middlewares and attaching Route to Request while sending to target controller, closure or endpoint middleware (so they known about it and can use for sub routing).

I have PSR-7 implemented now, router should be be used to use new Request and etc. Additionally i have to solve problem with controller aliases and use runtime instance of container.

I want to use abstract models for ODM and ORM in modules, which is fine (User extends AbstractORMUser) but for more complex modules like CMS manager (we have to make it not only for ODM but for ORM also) there is 8 models, not sure making each of them abstract will be effective.

Consider solution where model can say if it's "active" while indexing based on external service or config - "don't map me to database, there is primary model missing or module is disabled".

I can reuse router from the past, but PSR7 will be really good for request and response. Flow already prepared in comments.

There is some performance issues with cookie encrypting/decrypting in http dispatcher.

Current implementation uses code written 5 years ago, it has to be updated to something more modern.

Additionally CookieManager should become request specific.

Yeah, seems like not a lot of people love widescreen. Lowest priority for future.

I need ViewConfig write with abilities:

• add processor to default engine
• add namespace

I want to use internal routing in controllers and endpoint middlewares, i don't want to define routes in bootstrap for that.

Do i need inheritance in DataFilter? My gut says yes, performance says no (sort of, there is usually only one model per request?).

Will be nice to have ability to start spiral application with given php.ini on specified port and host. Think about beauty way to implement it.

I have to move status code and message into it.

Too much legacy code.

AC: Something with prebuilt routing to specified controller methods based on http method, easy but lazy.

Not really sure i want to extend SelectQuery for ORM selector so i will need this portion be available as separate code piece.