[Spike] Review performance regarding pagination between TreeList and TreeContent

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

This issue covers this pending discussion/discovery:

We realised that the initial design proposal has the file browser outside of the Tree app. In the current state of the architecture, that means a separate entry point in HAML and a new Vue app. Which as a consequence means, we can not share one paginatedTree query for both TreeList and TreeContent. This will have impact on the performance, we will brainstorm some ideas on how to manage that.

This highlights the inevitable need to unify Vue applications on the Repository page even further.

— @psjakubowska

and

Which as a consequence means, we can not share one paginatedTree query for both TreeList and TreeContent. This will have impact on the performance, we will brainstorm some ideas on how to manage that.

We also need to cater for rendering the file tree on the blob page, another reason to decouple from the Tree app. We can explore using Vuex/Pinia store that can be shared between the FileTree and TreeContent.

— @jerasmus

See thread: #525169 (comment 2457027791)