[Issue-571] make docs
errors/warnings fixes
#725
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #571
Summary
Stats:
ERRORs
error type 1 (count: 5, left unfixed)
example:
happens during notebooks pre-processing. It probably means that
nbsphinx
generated empty.. raw::
directives, without a content block.Do not know what effect it has or how to fix this/
Think, not worth spending time on it (at least currently)
error type 2 (count: 3, fixed)
example:
unexpected indentation in the docstring.
WARNINGs
warning type 1 (count: 5, fixed)
example:
we automatically generate references to the example
notebooks for the checks API pages, to make it work
properly we need to make sure that notebook names are
the same as checks names (but in snake case)
I fixed this
warning type 2 (count: 8, left unfixed)
example:
It happens during
autosummary
stub files generation, becausesphinx
tries to import something that cannot be imported.The reason for this is that
autosummary
provides incorrectvariables to the jinja template/ (That is probably a bug, because
it happens only for the inherited attributes)
As a result of this,
checks
, andname
attributes are notdisplayed on the
Suite
API Reference page.not worth spending time on it currently, will create a separate issue for this
warning type 3 (count: 107, left unfixed)
example:
indicates that documentation contains two or more identical titles.
In
sphinx
we can refer to other documents parts by their title with help of the:ref:
role,but it will not work properly if title duplicates exist, therefore sphinx prints a warning (I think/)
sphinx
ref
role docswarning type 4 (count: 348)
example:
napoleon
extension tries to generate links for all function parametertypes within docstring, when he fails he prints a warning
most of the warnings that I saw in the output were related to the cases
when it tried to generate a link to the third party routines, like pandas
or numpy.
I tried to use
napoleon_type_aliases
config option to actually generatelinks to other docs, but it worked partially/ links were present only on a few pages.
So, I abandoned that idea