-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Is there a way to turn off warnings? #108
Comments
Hi @facelessuser ! There currently is no way to silence these warnings.. but I agree there should be. More users are using This is the line causing the warning: mkdocs-git-revision-date-localized-plugin/mkdocs_git_revision_date_localized_plugin/util.py Lines 169 to 175 in 7ddc74c
Your specific example is not related to the I see some options:
I prefer the first option. Will try to pick this up somewhere this week! |
Sounds great! I'm agnostic to how they get silenced as long as it is possible 🙃. I'm fine with option 1. |
New release |
For future reference, to turn off warnings, you can now in your plugins:
- git-revision-date-localized:
strict: false |
I have some documentation tests that build the documentation in strict mode to find any issues and then runs a spellchecker on the output afterward. I find it very frustrating that I get these warnings in particular:
I've specifically enabled the following to handle the fact that the file has no history yet I still get the warning which fails the build.
I want the tests to be able to pass in a release bundle that does not have git, so I need this warning to be optional if at all possible.
Are the warnings really necessary if I've explicitly told it to fallback to build date? Or can we make such warnings optional?
The text was updated successfully, but these errors were encountered: