feat: Lazy Loading of Sub categories #1586
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…render the configured level of sub categories * "lazy loading" of sub categories for the main navighation only on client side * reduce rendered main navigation code in SSR rendered HTML * reduce categories content of the transfer state * decrease needed tranfer size per SSR page
shauke
force-pushed
the
feature/sub-categories-lazy-loading
branch
from
5be227c
to
750c9cf
Compare
shauke
added
performance
shauke
approved these changes
Mar 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Type
[x] Feature
[x] Other: performance improvement
What Is the Current Behavior?
Currently, the configured level of main navigation categories (
mainNavigationMaxSubCategoriesDepth) is loaded already on the server side. Therefore the SSR rendered HTML page contains a lot of unneeded category data (main navigation HTML, transfer state, transfered REST call content).What Is the New Behavior?
The goal is to reduce the load time/size of HTML pages in the project. Only the top-level categories are now being loaded and rendered on SSR while the sub-level categories are loaded and rendered on the client side.
Does this PR Introduce a Breaking Change?
[x] No
Other Information
AB#94097