Multi-line NumPy-style return descriptions without a type get rendered wrong

[ExplodingCabbage]

Here's a docstring actually taken from NumPy:

"""
Collect arguments on which to call __array_function__.

Parameters
----------
relevant_args : iterable of array-like
    Iterable of possibly array-like arguments to check for
    __array_function__ methods.

Returns
-------
Sequence of arguments with __array_function__ methods, in the order in
which they should be called.
"""

Napoleon butchers the return description, treating each line as a list item:

I don't think there's currently any way at all to get this multi-line return description like this to render correctly using NumPy style.

[rdbisme]

@ExplodingCabbage The | operator should help, shouldn't it?
Here I made some progress: https://github.com/agronholm/sphinx-autodoc-typehints/issues/130, but I lost type hinting.

In your case I think this works (first line is |<space><space>)

Returns
-------
|  
  Sequence of arguments with __array_function__ methods, in the order in 
  which they should be called.

[jkochNU]

Are there any plans for addressing this? As pointed out above, the workaround using | leaves sphinx-autodoc-typehints broken...

[cthoyt]

+1 on this. Like @jkochNU I am also patiently awaiting a solution