c-parsons

This is an extension of bazelbuild/skydoc#182 and a duplicate of bazelbuild/skydoc#115 (though contains more detail than the original FR issue)

My proposal is that it appends the additional docstring to that of the inherited rule. In other words, bin_output for the macro would have docstring: "Binary output. `name` + '.exe'...

Sure. Lets address these by using a metatag per arg as well. ```python def my_rule(name, otherarg, **kwargs): """@inherit(_my_rule) Args: bin_output: @argdoc(_my_rule.bin_output). `name` + '.exe' by default. otherarg: Some new argument....

I assume you mean, for definition of `my_rule`: ```python def my_rule(name, foo="different_default", **kwargs): """@inherit(_my_rule) Args: foo: @argdoc(_my_rule.foo). more text here. """ _my_rule(name = name, foo = foo, **kwargs) ``` (note...

For what it's worth, in your above example, it wouldn't be appropriate to have `foo` under the `Args` section of the function docstring, as it is not an actual requires...

Stardoc **can** indeed handle .bzl files from remote repositories. Can you provide some more details on how to reproduce this error? As an example, Stardoc [self-documents](https://github.com/bazelbuild/skydoc/blob/master/test/self_doc_golden.md) its Starlark rule ([stardoc.bzl](https://github.com/bazelbuild/skydoc/blob/82fdbfe797c6591d8732df0c0389a2b1c3e50992/stardoc/stardoc.bzl)),...

Aha. I'll take a look. Thanks for the info.

As in you'd like Stardoc to retrieve and relay information about a top-level comment? Lets file a separate FR for that, if you need it. Are you able to get...