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

[BUG] Incorrect Path to Files if no markdown in root folder #524

Closed
Chris3773 opened this issue Mar 30, 2018 · 3 comments
Closed

[BUG] Incorrect Path to Files if no markdown in root folder #524

Chris3773 opened this issue Mar 30, 2018 · 3 comments

Comments

@Chris3773
Copy link

Overview of the issue

In the version 1.1.1 of compodoc the paths that are created are pointing to the wrong location.

compodoc -p tsconfig-build.json -d ./docs --disablePrivate --disableInternal --theme material

Version 1.0.9:
image

Version 1.1.1:
image

Operating System, Node.js, npm, compodoc version(s)

compodoc: 1.1.1
Typescript version : 2.8.1
Node.js version : v8.9.4
Operating system : Windows 10

Angular configuration, a package.json file in the root folder
Compodoc installed globally or locally ?
Motivation for or Use Case
Reproduce the error
Related issues
Suggest a Fix
@vogloblinsky
Copy link
Contributor

Hi

I cannot reproduce this issue with your environment.

In which page did you see href=".../styles/material.css" ?

Thanks

@Chris3773
Copy link
Author

Looking more into the issue it's only a problem for the "index.html" file.

On a hunch I added a README.md file to my project and tried again and it worked just fine. So the issue only happens when the project is missing a README.md file.

@vogloblinsky vogloblinsky changed the title [BUG] Incorrect Path to Files [BUG] Incorrect Path to Files if no markdown in root folder Apr 2, 2018
@lock
Copy link

lock bot commented Sep 30, 2019

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. Why locking ? Having issues with the most up-to-date context.

@lock lock bot locked as resolved and limited conversation to collaborators Sep 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants