Daniel Cousens

> Why remove the Function | { ... } hook syntax? [Replying to myself] we did actually talk about this at length, but opted to keep things aligned with the...

@kennedybaird I think adding a checkbox (or cookie, or) that can easily switch between different field modes will be incredibly helpful in debugging UX

`tests/sandbox`, but I think we can defer to @jossmac to know if that is useful in this pull request, or separately

@gautamsi > I believe this is a blocker for https://github.com/keystonejs/keystone/pull/9186? Yes, I think this is blocking > Do you have any figma/design link we can provide feedback on? Unfortunately, the...

@gautamsi I think a significant amount of time is needed for QA and documenting or resolving any regressions, maybe the next step is an alpha RC

@gautamsi #9186 and this going out together, and soon, an an alpha sounds good to me; let's try for next week

@gautamsi I can't reproduce that, did you have a `config` you could share?

This pull request is pretty big, and we could probably keep working on it for quite a while, but it's time to move to the next phase and put out...

@gautamsi this is intended, and arguably the only reasonable option when you have nested operations. The underlying problem is that we have emphasised that `beforeOperation` and `afterOperation` should be used...

@AdamBerri @flippinjoe do you have a minimal reproduction that I can use to add tests for this? I'm not following exactly what behaviour you had previously compared to now.