Dash
Dash
anidb has very fascist rules for API queries. Just my two cents.
Why not pass `t.__doc__` to `parse` directly?
I think I'd need to see a MVP to comment whether we should support this. (probably yes) My preliminary intuition is that I wouldn't want to extend `parse`'s contract by...
Fair, but how would you extract the docstring for `attr_one` and `attr_two`?
It looks good. Regarding how to introduce this feature, I don't have a better suggestion than this – introduce a top level function similar to `parse` that does the thing...
Also in Google style if we have: ``` """Arguments: argument: long description, long description 2 """ ``` I'd expect `long description 2` to be indented with 4 spaces (relative to...
Thank you for the detailed report. Currently this feature isn't there and would need to be implemented.
I wouldn't add a new flag and just always keep the original indentation – it's easy to emulate old behavior with `"\n".join(map(str.strip, docstring.splitlines()))`.
Where can I read more about this syntax? The reason it gets parsed as `long_description` is because the Google parser crashes, thinking `Example:` is an empty section, and `.. testcode::`...
The crash is now fixed in 0.9.1, although the example won't parse properly.