Tobias Lode

Could it be that this is just a configuration problem? I've had copied this example from the API Reference ``` $breadcrumbProvider.setOptions({ prefixStateName: 'home', template: 'bootstrap2' }); ``` without having the...

Why not make explicit setters? for example `flagPersisted()` for state EXIST, `flagModified()` for state MODIFIED and `flagNew()` for state NONE.

But they could work like `StatefulEntityTrait::touch()` ``` php $this->status |= FlexibleEntityInterface::STATUS_MODIFIED; ``` Then, one can check a specific state with a method like `flaggedModified()` ``` php public function flaggedModified() {...

Or put those things in a separate state object, for example ```php $entity->meta()->touch(); $entity->meta()->isModified(); $entity->meta()->setStatus(); ```

@mvrhov is right, that would be a bit of an overhead. It depends on the implementation. If a `meta` instance could be shared between entities, adding a reference wouldn't be...

Last time I thought about updating entities, I came up with a idea to rewrite the `Where` helper and let it base on a similar concept named `Expression`. The idea...

:+1: Still, I believe that even `UpdateExpression` is still a specialized implementation of a more generic `Expression` object. It could generally introduce handling of numbered parameters like `a = $1`...

I've also experimented with the approach of using a pcre as a specific composite literal parser. Best I've got so far is the one I've found here https://regex101.com/library/oU3yV6 The idea...

I agree. This was more of an experiment I wanted to share. So what could be a solution then? It is obvious to me that `str_getcsv` isn't the right solution...

I am using `begin` / `rollback` in tests in the way you described. But as my `ModelLayer` classes, which I want to test, use transactions itself, I need the ability...