Andreas Allacher

Disabling states works for me this way. However, for some reason the first step (also Sylius) `cart` always seems to be gone too. Furthermore, why not just `stateName: false` or...

Well, You can still extend it using packages which basically allows one to disable existing transitions / states like mentioned above in this thread. Of course, it can be done...

Yes. But as mentioned, if you are not using Sylius, you might have to make some changes but I guess it should just be (as mentioned above) this overridden method:...

@cseufert Not 100% sure about the best solution either but to behonest I don't find you suggestion that bad as it would be similar to how a switch is formatted...

@cseufert Looks good. Though I think moving the `=>` to a new line and using some indentation might be better as one sees that a new case chain starts more...

@cseufert Maybe some other formatting rule that runs after match is formatted? Though I guess it is unlikely as it could lead to interesting cross results but not impossible.

Actually the same issue would exist with delete. And then there are some other issues like e.g.: - Client 1 creates record `a`. - Client 1 goes offline. - Client...

After looking at firemelonDB we made some changes: - Add a session (for pull/push set) - Provide any changes in the push and add it in another synchronize as pull...

@mtford90 What I did now was that during push, after the changes were applied, I immediately return all changes sind the last pulled with a new last pulled at timestamp....

Not sure if using versioning is a good solution as in theory multiple clients could arrive at the same version at the same time. I used a randomly generated session...