I have seen errors like Failed to get 'name: description' pair from '', which even given the name of the docstring, can be hard to track down.
It would be really nice if every error message always included a line number.
It would be even better if all line numbers were reported as actual source lines using a format that
IDEs will recognize so that you make. For instance, pylint will prefix each error with a <filepath>:<line#>:.
It makes fixing errors MUCH easier for the user.
Griffe should already behave better regarding line numbers in warnings. But I guess we can leave this open as a simple improvement/bugfix for the time pytkdocs will continue to be used in projects, through the legacy handler.
I have seen errors like
Failed to get 'name: description' pair from ''
, which even given the name of the docstring, can be hard to track down.It would be really nice if every error message always included a line number.
It would be even better if all line numbers were reported as actual source lines using a format that IDEs will recognize so that you make. For instance, pylint will prefix each error with a
<filepath>:<line#>:
. It makes fixing errors MUCH easier for the user.