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

always in strict mode? #150

Closed
jtuttas opened this issue Jan 28, 2022 · 5 comments · Fixed by #199
Closed

always in strict mode? #150

jtuttas opened this issue Jan 28, 2022 · 5 comments · Fixed by #199

Comments

@jtuttas
Copy link

jtuttas commented Jan 28, 2022

Hello, I just try you action, but the run abort with the message:

WARNING - Documentation file 'Beispiel2.md' contains a link to 'docs/images/test.svg' which is not found in the documentation files.
WARNING - Documentation file 'Beispiel2.md' contains a link to 'docs/tier.uxf.svg' which is not found in the documentation files.

Aborted with 2 warnings in strict mode!

But in my mkdocs.yml I disbaled the strict mode...

site_name: MyTest

strict: false

nav:
    - Home: bsp.md```
@jtuttas
Copy link
Author

jtuttas commented Jul 9, 2022

Any Help for this issue?

@dalonsoa
Copy link
Contributor

Same here. strict: false in the config seems to be ignored. I can see the point on having it enabled by default, but it should be possible to manually overwrite that behaviour with the config.

@dalonsoa
Copy link
Contributor

The issue seems to be here, where the information in the config file is overwritten... :(

exec -- mkdocs build --config-file "${CONFIG_FILE}" --strict

@mhausenblas
Copy link
Owner

PR appreciated if anyone has the cycles

@dalonsoa
Copy link
Contributor

Oh, I can certainly do it - it is a one line change! The question is to know the rationale for forcing the strict mode and to be aware that his might be a breaking change.

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

Successfully merging a pull request may close this issue.

3 participants