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
SubConfig now catches failures and warnings #2710
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay
Great, no worries @oprypin ! |
Oops, unfortunately this makes a test fail. https://github.com/mkdocs/mkdocs/runs/5702600210?check_suite_focus=true#step:5:19
That makes me think that there are probably unforeseen negative implications from this change, so I'll have to revert it until further investigation. |
Indeed, sorry. Sad that the CI was not executed on PR :( . Maybe something to consider in the future ? |
Update : I was able to test outside of tox, directly in PyCharm.
Therefore there was an error in the subconfig The fix is now doing its job correctly, showing the error to the user. Now the decision to take with this test is "should the 'extra' config option in the default schema accept any kind of options inside it ?". If the answer is yes, we should probably define a constructor flag in Let me know ! |
@smarie If I understand correctly, the |
Fixes #2709