Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: collapse root sidsebar items#1979

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
proke03 wants to merge9 commits intodocsifyjs:develop
base:develop
Choose a base branch
Loading
fromproke03:feat/collapse-root-sidebar-items

Conversation

@proke03
Copy link

@proke03proke03 commentedJan 29, 2023
edited
Loading

Summary

What kind of change does this PR introduce?

For any code change,

  • Related documentation has been updated if needed
  • Related tests have been updated or tests have been added

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:

Related issue, if any:

#900

Tested in the following browsers:

  • Chrome
  • Firefox
  • Safari
  • Edge
  • IE

@vercel
Copy link

vercelbot commentedJan 29, 2023
edited
Loading

The latest updates on your projects. Learn more aboutVercel for Git ↗︎

NameStatusPreviewCommentsUpdated (UTC)
docsify-preview✅ Ready (Inspect)Visit Preview💬Add feedbackApr 19, 2023 10:27am

@codesandbox-ci
Copy link

codesandbox-cibot commentedJan 29, 2023
edited
Loading

This pull request is automatically built and testable inCodeSandbox.

To see build info of the built libraries, clickhere or the icon next to each commit SHA.

Latest deployment of this branch, based on commit2daba85:

SandboxSource
docsify-templateConfiguration

html=this.compile(text)
.replaceAll('<ul >','<ul class="app-sub-sidebar" >')
.replace('<ul class="app-sub-sidebar" >','<ul >');
}else{
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

what is this change for ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

text is the entire compiled html of the sidebar.
The first "ul" is an element that contains the entire sidebar menu.
So I tried to give a class to the rest of the "ul" except the first "ul".
캡처_2023_02_05_19_16_53_1

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

text is the entire compiled html of the sidebar. The first "ul" is an element that contains the entire sidebar menu. So I tried to give a class to the rest of the "ul" except the first "ul".캡처_2023_02_05_19_16_53_1

I see, you gonna treat the parent sidebar node as the sub-sidebar of the rootul.
But the class.app-sub-sidebar you marked get the style change as well.

Before:
image

After:
image

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Maybe you could marked those parent sidebar nodes with new styleapp-sidebar and refactor theclick event function.

Copy link
Author

@proke03proke03Feb 28, 2023
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

In my opinion, implementing it with onClick seems to be a dual implementation method for one feature.
So I implemented it by className, which is the way used before.

@Koooooo-7Koooooo-7 requested a review froma teamFebruary 6, 2023 05:43
Copy link
Member

@Koooooo-7Koooooo-7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

LGTM.

@Koooooo-7Koooooo-7 self-requested a reviewMarch 1, 2023 09:45
@Koooooo-7Koooooo-7 requested a review froma teamMarch 1, 2023 09:45
Copy link
Member

@trusktrtrusktr left a comment
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This is great! Can you please:

  • ensure the top-level items seem like they are clickable (instead of seeming like selectable text), using for examplecursor: pointer.
  • write a test for the functionality
  • We need to ensuredocsify-themeable doesn't break with this. Add a newdocsify-themeable.html file that uses docsify-themeable so we can verify. Perhaps we should do this first in a separate PR.

@proke03
Copy link
Author

@trusktr
The themeable file is an extension of docsify.
In themeable, style is specified.
So, in order for changes in docsify to be applied without changing themeable, the id and class values previously specified in themeable must not be applied elsewhere.
Is my understanding correct?

@trusktr
Copy link
Member

@proke03 basically the docsify-themeable CSS depends on the DOM of Docsify.

I think what we should do is in a totally separate pull request lets get a docsify-themeable deployment for n Vercel going, and then it will be available to all PR similar to our current Vercel deployment with vanilla Docsify.

@PowerPlop
Copy link

It seems this PR is abandoned,@trusktr is it still relevant to continue with the last tasks you listed?

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@trusktrtrusktrtrusktr requested changes

@Koooooo-7Koooooo-7Koooooo-7 approved these changes

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@proke03@trusktr@PowerPlop@Koooooo-7

[8]ページ先頭

©2009-2025 Movatter.jp