Skip to content
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

Sidebar Configuration in sidebars.js file #707

Open
inhwaS opened this issue Oct 25, 2024 · 1 comment
Open

Sidebar Configuration in sidebars.js file #707

inhwaS opened this issue Oct 25, 2024 · 1 comment
Labels

Comments

@inhwaS
Copy link

inhwaS commented Oct 25, 2024

What package is your question related to?

typedoc-plugin-markdown

What would you like to ask?

Hello, I would like to ask another question in extenstion for #705 .
Based on this change log, it is guided to do:
Screenshot 2024-10-25 at 10 48 22

Does it mean that I should not use like code like:
https://github.com/facebook/lexical/blob/e96ee55b749c0fed8ac03d49044dd5594f0bc32e/packages/lexical-website/sidebars.js#L23-L25

Since it automatically creates so many files, I’m concerned that I will need to document all the markdown files, as the autogenerated process creates roughly 50 files in total. Can I ask how people typically handle updates?

@tgreyuk
Copy link
Member

tgreyuk commented Oct 25, 2024

Hi @inhwaS,

Rather than reference type: "autogenerated" you would reference the auto generated sidebar.

So you would replace:

  api: [{dirName: 'api', type: 'autogenerated'}],

with (you might need to tweak the path but this is the general idea):

api: [{
      type: 'category',
      label: 'api',
      link: {
        type: 'doc',
        id: 'api/index',
      },
      items: require('./docs/api/typedoc-sidebar.cjs'),
    }],

So you wouldn't need to worry about managing the files - the autogenerated sidebar will do that.

Hope this makes sense.

Let me know how you get on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants