Mark Story

Fields by default are not allowed to be empty. You need to set `allowEmpty()` on the field to make it not required.

That is odd. I'm reluctant to change the behavior in a bugfix release because it will most likely cause problems in userland applications as previously required fields become no longer...

> Or should be fixed and included in 4.3? I don't know how we change the behavior and also have it be 'backwards compatible' at the same time.

> Is there anything left to do for this? We could update FormHelper to detect whether or not a field is required to be non-empty so that the required attribute...

> Can tables specify a role? I think we should have read/write configuration at the query level, and have affordances at the table level to set defaults. Having role configurations...

> This implies having a separate Connection instance for each role. That makes sense for some reasons, but would conflict with the idea of still having a a test or...

> Should the read and write roles share a schema cache or maintain separate copies? I would start with separate. There are scenarios where not all tables from a primary...

The code snippets you have show the more static properties. Won't those have the same problems as we have today? Or do you use the `RouteContext` instead of `Router` in...

> $this->routeContext = new RouteContext([], $this->request); I don't love this as a user-facing API. We should try to provide a high level API that covers common usage. What do you...

> There's no stack, we removed it when we got rid of the "request action" feature. I am not too thrilled about re-introducing a request stack in the Router. Totally...