-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
refactor(theme-classic): extract common PaginatorNavLink component #6213
Conversation
✔️ [V2] 🔨 Explore the source changes: 28e1931 🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/61cbdb0beea2d30007f204b5 😎 Browse the preview: https://deploy-preview-6213--docusaurus-2.netlify.app |
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-6213--docusaurus-2.netlify.app/ |
Size Change: 0 B Total Size: 667 kB ℹ️ View Unchanged
|
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.
Thanks, LGTM 👍
import Link from '@docusaurus/Link'; | ||
import type {Props} from '@theme/PaginatorNavLink'; | ||
|
||
function PaginatorNavLink(props: Props): JSX.Element { |
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.
not a big deal for now, but this is bad encapsulation that Infima is using a --next
suffix in parent class to determine the position/direction of the arrow. This should be a props instead of a parent class, and this component should be self-sufficient to render properly without using any parent CSS
Motivation
Fix #6171.
PaginatorNavLink
component.Have you read the Contributing Guidelines on pull requests?
Yes