We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
typedoc-plugin-markdown
The documentation for typedoc states, https://typedoc.org/options/output/#githubpages:
typedoc
--githubPages Generate a .nojekyll file to prevent 404 errors in GitHub Pages. Defaults to true
true
There is no .nojekyll file generated, and if there is a .nojekyll file, it is deleted.
.nojekyll
touch docs/.nojekyll typedoc --plugin typedoc-plugin-markdown
FYI: I opened an issue in typedoc, TypeStrong/typedoc#2635, and it was mentioned that the plugin may be overriding
Expecting a .nojekyll file in the destination output folder.
The text was updated successfully, but these errors were encountered:
Well, I guess I needed to fully read the documentation...https://typedoc-plugin-markdown.org/docs/typedoc-usage
Sorry, something went wrong.
This seems like a reasonable request - if there is a use-case for this id be happy to implement.
feat(core): write .nojekyll file if TypeDocs "githubPages" option i…
d8b983d
…s true (#650)
@scottschreckengaust githubPages has been implemented in typedoc-plugin-markdown@4.2.0. It "false" by default.
githubPages
No branches or pull requests
What package is the bug related to?
typedoc-plugin-markdown
Describe the issue
The documentation for
typedoc
states, https://typedoc.org/options/output/#githubpages:There is no
.nojekyll
file generated, and if there is a.nojekyll
file, it is deleted.FYI: I opened an issue in
typedoc
, TypeStrong/typedoc#2635, and it was mentioned that the plugin may be overridingTypeDoc configuration
Expected behavior
Expecting a
.nojekyll
file in the destination output folder.The text was updated successfully, but these errors were encountered: