-
Notifications
You must be signed in to change notification settings - Fork 43
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
feat(theme-default): improve sidebar headers #196
Conversation
Pull Request Test Coverage Report for Build 9380781281Details
💛 - Coveralls |
|
||
defineSlots<{ | ||
'top'?: (props: Record<never, never>) => any | ||
'bottom'?: (props: Record<never, never>) => any | ||
'content-top'?: (props: Record<never, never>) => any | ||
'content-bottom'?: (props: Record<never, never>) => any | ||
}>() | ||
|
||
setupHeaders() |
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.
Why not place it in sidebar
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.
The new headers need to wait for the <Content />
component to be Mounted
before being read from the DOM. The <VPPage />
component can ensure that the DOM is Mounted
, but placing it in the <Sidebar />
cannot guarantee this. Additionally, reading and generating new content to be inserted into the DOM after being Mounted
may trigger onMounted
again, causing unnecessary repeated calls and potentially leading to new issues.
Before submitting the PR, please make sure you do the following
close #123
).What is the purpose of this pull request?
Description