spiral-modules / components Goto Github PK

Find places where contructor in interface can be dropped in order to be replaced with setter.

Technically i can always add RequestAwareMiddleware in future and tweak pipeline a little bit. Not a huge problem. The only problem will be to link two interfaces to each other to let some methods (do i have any methods with MiddlewareInterface type?) accept both interfaces. In any scenario it's not hard to generate and pass response thought pipeline and make it accessible for controller.

Should i do it sooner and before release? Maybe.

As fallback layer under spiral translation bundles.

Not sure if logger() method is good idea, change to logger property, not empty and container registration (isolate container branch)

Easy to do since we can use same exact way as for abstract classes.

:/ using finder

And allow to use custom ORM entities. Must include:
__constuct (data, loaded, orm, schema) //from outside
isLoaded
primaryKey
setField ?
getField ?
...

i can also define multiple type of RecordSchemas to read different formats.

seems overcomplicated as shared env can be scoped using try finally block, hmmm, maybe i don't need setContainer method but i do need this changes i did in container (registerInstance)

Plus convert $exception variable to $e where possible

To think before beta release.

Right now i have a scalar values as fallback, i can remove it to make code cleaner.

So global sorting or constrains will work, write in docs about it

Oops

Simply define more exception types, create valid tree. @see PDODriver::clarifyException

Interfaces must be constrained. No breaking changes must happen.

basically cache invalidation but faster than full re-scan

Add support for window pagination (easy).

Must work perfectly with middleware endpoint but i'm not sure if will work inside middleware itself - it probably should as middleware dot not contain hidden code.

I think i should add type constrain for parent (EntityInterface), do we need to pass container instead of ODM/ORM?

To be changed before release, easy to do.

Ideally I want to use Orm model same way as odm

So they can be represented as the same repository.

exception should't be thrown if undefined field passed into setFields method, just supress it