-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
fix($theme-default): remove error logs for nested sidebar groups #2191
Conversation
This arbitrarily logged out when nesting was greater than 3. ``` 07:58:13.598 [vuepress] detected a too deep nested sidebar group. 2 2.258cb917.js:1:3364 ``` vuejs#2190
Hi @KieranHunt I think this is because initially, VuePress was not supporting nested sidebar items indentation if it was higher than 3. But it supposed to be fixed with #1973. Could you confirm the indentation is correct when nesting is more than 3. |
Also could you fix parts of the docs saying the maximum is 3? |
Set up a toy project
module.exports = {
themeConfig: {
sidebar: [
'/',
{
"title": '1',
"children": [
{
title: '2',
children: [
{
title: '3',
children: [
{
title: '4',
children: [
{
title: '5',
path: '/1/2/3/4/5/'
}
]
}
]
}
]
}
]
}
]
}
} Get a bunch of errors in my console:
Here's a very tiny gif of it working: |
Will hunt around and try find the bits of the docs that refer to 3. |
The warning about the nested sidebar group is at the bottom of sidebar-groups section.
|
Thanks @ludanxer! Just checking in to say I haven't forgotten about this PR. Have just been super busy. |
I'm going to merge this PR first, and remove the warning in docs in another commit |
This arbitrarily logged out when nesting was greater than 3.
#2190
Summary
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
N/A
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
N/A
The PR fulfills these requirements:
fix #xxx[,#xxx]
, where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:
Opened an issue here: #2190