You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are far too many "silent" errors, where the sidebar or pages simply don't show up, and no error is produced. For example, if you configure themeConfig.sidebar to refer to a nonexistent link, or links to what appear to be "special" files (e.g. "index"), the sidebar will simply disappear in its entirety.
Note this is with vuepress/1.0.0-alpha.47 linux-x64 node-v11.14.0, run with vuepress dev --no-cache --no-clear-screen --debug.
Another example appears to include markdown parsing errors, which simply cause pages to disappear rather than display any reason.
What does the proposed API look like?
No API.
How should this be implemented in your opinion?
Running vuepress dev should at a minimum spit out errors to the console; ideally any parsing errors should appear instead of the page in question, or specific errors (missing sidebar entries) should be hilighted in-page.
Are you willing to work on this yourself?
Not really.
The text was updated successfully, but these errors were encountered:
Feature request
What problem does this feature solve?
There are far too many "silent" errors, where the sidebar or pages simply don't show up, and no error is produced. For example, if you configure
themeConfig.sidebar
to refer to a nonexistent link, or links to what appear to be "special" files (e.g. "index"), the sidebar will simply disappear in its entirety.Note this is with
vuepress/1.0.0-alpha.47 linux-x64 node-v11.14.0
, run withvuepress dev --no-cache --no-clear-screen --debug
.Another example appears to include markdown parsing errors, which simply cause pages to disappear rather than display any reason.
What does the proposed API look like?
No API.
How should this be implemented in your opinion?
Running
vuepress dev
should at a minimum spit out errors to the console; ideally any parsing errors should appear instead of the page in question, or specific errors (missing sidebar entries) should be hilighted in-page.Are you willing to work on this yourself?
Not really.
The text was updated successfully, but these errors were encountered: