Nico Hoffmann ෴.

We talked about this again at length in the team and this is really more an enhancement/feature request that we need to move over here https://kirby.nolt.io/528 for now as we...

> It just means, it's not gonna happen. If you check the roadmap on Nolt right now you'll see that there are things already flagged as in Kirby 4 with...

@lukasbestle we abandoned the idea of caching over here https://github.com/getkirby/kirby/issues/3548 - but we never did really test the performance hit from calculating on-the-fly, did we?

@lukasbestle let's go with option 1 - seems to me as well the more sensible choice. As I understand it, our implementation that uses `AND` logic already came up due...

@lukasbestle Not debating that this is a breaking change, we're only talking about the dimensions of the breaking change and if/how to ease it. From your descriptions above, the feature...

I'm still trying to understand why it would be so difficult. Yes, it'll be a breaking change by definition, but would it be really a problem for the vast majority?...

Also trying to breathe life into this one again: I've read the long discussion back and forth. What I gathered: ## `AND` vs. `OR` Currently, the logic is rather exclusive...

The issue is that loading one view can trigger multiple `onFinish` when one requests finishes loading before other asynchron requests even have been started.

I think remembering the height plus skeleton will be quite the hack as we this would easily fail with any custom sections right now. Personally, I think we need a...

I have to admit I gave unit tests a try once but failed and abandoned it quickly 😅🙈