-
Notifications
You must be signed in to change notification settings - Fork 28k
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
[SPARK-46151][PYTHON][DOCS] Hide the More drop-down button
in the PySpark docs navigation bar
#44068
Conversation
…ySpark docs navigation bar
@@ -196,6 +196,7 @@ | |||
# further. For a list of options available for each theme, see the | |||
# documentation. | |||
html_theme_options = { | |||
"header_links_before_dropdown": 6, |
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.
default value is 5
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.
Oh, I was also thinking of fixing this.
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.
LGTM.
More" drop-down button
in the PySpark docs navigation barMore drop-down button
in the PySpark docs navigation bar
I guess maybe you wanted to apply the style something like: Hide the "More" drop-down button in the PySpark docs navigation bar or Hide the But it's not a big deal, so the PR looks still good to me :-) |
Merged to master. |
What changes were proposed in this pull request?
The pr aims to hide the
More drop-down button
in the PySpark docs navigation bar.Why are the changes needed?
Because there is
only one item
under theMore drop-down button
, as following:Obviously, in our scenario, eliminating
More drop-down button
and directly displayingMigration Guides menu
in the navigation bar is more intuitive and convenient.After:
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually test.
Was this patch authored or co-authored using generative AI tooling?
No.