Suppress warning messages in documentation#1991
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1991 +/- ##
=======================================
Coverage 100.0% 100.0%
=======================================
Files 278 278
Lines 22714 22714
=======================================
Hits 22705 22705
Misses 9 9 Continue to review full report at Codecov.
|
Ooh good point. I agree. I didn't think of that when we were considering the options. @bchen1116 is there any way around that? |
|
Moving forward with the current hidden cell method, but filed an issue here to track simplifying this |
ParthivNaresh
left a comment
There was a problem hiding this comment.
Looks good man, what was the outcome of the configuration file we were looking at before?
|
@ParthivNaresh I couldn't get the config file to work out. I think ReadTheDocs ends up looking at a different file on their side, so I sent them an email to follow up on how we can get our config in/update the path! |
fix #1887
I decided to add hidden cells that caught the warning messages in each notebook. However, it might confuse users when the first code cell execution starts at [2] instead of [1].
Adding a warning into

explain_predictions():Having the warning in

explain_predictions(), but also catching warnings in notebooks: