-
Notifications
You must be signed in to change notification settings - Fork 23
Optimize lazy load navigation #1514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
public required string Id { get; init; } | ||
} | ||
|
||
public record EmptyNavigationRenderResult : INavigationRenderResult |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be a static property on OkNavigationRenderResult
?
e.g OkNavigationRenderResult.Empty
then we can just have a single record NavigationRenderResult
without an interface.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
src/Elastic.Documentation.Site/Navigation/INavigationHtmlWriter.cs
Outdated
Show resolved
Hide resolved
…r.cs Co-authored-by: Martijn Laarman <Mpdreamz@gmail.com>
Context
follow-up from #1505
Currently we are create a .nav.html file for every page that exists.
However, there are many duplicates as the navigation for sub pages are probably the same.
Changes