Build should fail when strict mode and warnings #86
Comments
pawamoy
added a commit
that referenced
this issue
Apr 14, 2020
With strict mode (`-s` option for build and serve commands of MkDocs), the build should fail if any warning has been issued. This was not the case. This commit adds the `warning_filter` counter declared and used by MkDocs to loggers in all modules. Reference: #86.
pawamoy
added a commit
that referenced
this issue
Apr 14, 2020
With strict mode (`-s` option for build and serve commands of MkDocs), the build should fail if any warning has been issued. This was not the case. This commit adds the `warning_filter` counter declared and used by MkDocs to loggers in all modules. Reference: #86.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the warning will not make the build fail.
Hook properly the loggers so that the build fails if any warning has been issued.
Additionally, any log with level greater than warning should also make the build fail, let's see what happens in mkdocs/mkdocs#2064
The text was updated successfully, but these errors were encountered: