Question regarding if deeply nested reusables affect performance.
I tried to search for information on this topic but I haven’t found much. Ive been learning code for more advanced features and realised how reuseable code can be. And was wondering if I could stop repeating the same things over and over in bubble.io. But I’m not sure how bubble.io will handle it. I am wanting to break every reusable component/section into reuseable and use those with in reusables. Deeply nested reusables multiple layers deep. Does anyone have any experience doing this? Did this cause any issues in terms of performance?
Some examples, have a specific icon with certain effects as reuseable, text that can be clicked and copied as reuseable, workflows for basic calculations, and so on.
Would love any experience people have had with this. Otherwise ill try it myself and share any findings I find
Sorry for the delayed reply. All over the place, I am haha
Thanks for the message. yeah I’ve checked out that book, overall good but I don’t think touched on nested reusables but ill check again.
In the bubble docs it does say it can significantly slow it down, but was curious if anyone actually ran into that issue https://manual.bubble.io/core-resources/elements/reusable-elements