inside my Builder Field userts have the possibility to predefine various fieldsets in a blueprint that can then be combined as builder blocks in the panel. Since such blueprint configurations can become very complex, especially when the builder is nested, it makes sense to split them into different files using extends. Accessing all those different files seems to be a real performance bottleneck when the builder setup is rather complex and has a lot of nested extends.
Does Kirby use some kind of asynchronous file handling under the hood that could be adapted by me to solve this issue?
My current approach was to outsource the asynchronicity to the frontend and split it into several requests to the backend. However, this is also not a perfect solution for a number of reasons.