Are you on the latest chainladder version?
Describe the bug in words
Continuing with the theme of tech debt cleanup for the 1.0 release. There are lots of warnings issued when building the docs. I don't think there are quite as many as there are for #840, so I think this could be a 1-person job, but feel free to create sub-issues if you think the scope will require multiple PRs.
How can the bug be reproduced?
Run jb build . on a clean docs folder (make sure the _build folder is deleted before you run.)
...
build succeeded, 400 warnings.
What is the expected behavior?
There should be 0 warnings. I don't think we need to make room for weird irreconcilable edge cases. If certain docs files aren't assigned to toctrees because they're still in-progress, we should move them to experimental forks.
Are you on the latest chainladder version?
Describe the bug in words
Continuing with the theme of tech debt cleanup for the 1.0 release. There are lots of warnings issued when building the docs. I don't think there are quite as many as there are for #840, so I think this could be a 1-person job, but feel free to create sub-issues if you think the scope will require multiple PRs.
How can the bug be reproduced?
Run
jb build .on a clean docs folder (make sure the_buildfolder is deleted before you run.)What is the expected behavior?
There should be 0 warnings. I don't think we need to make room for weird irreconcilable edge cases. If certain docs files aren't assigned to toctrees because they're still in-progress, we should move them to experimental forks.