Francisco Giordano

Private items should always be omitted automatically. It doesn't make sense to document them as they are not part of the interface. Internal items you can omit by filter by...

Hi @dimsome. Modifiers are not exposed currently. By "available to the public" do you mean you want to remove stuff that is `onlyOwner` or similar? That is interesting... In the...

Hi @sergorl! Thanks for asking. I haven't been able to write a guide yet, so the best I can offer is my help. You should definitely use the `-t` option,...

Unfortunately there is no reference document with the available fields you can use in your template, but you will find them all in [this source file](https://github.com/OpenZeppelin/solidity-docgen/blob/b0fc871d6de8c915eaffec390f61f8347675edb1/src/solidity.ts). If you need more...

@d1onys1us I've added the `eq` helper by default in the latest release. Feel free to share a link to a repo if you need further help I can take a...

This is a problem with the Solidity compiler. I might be able to work around it with some effort but it really needs to be fixed upstream. See https://github.com/ethereum/solidity/issues/12295.

This should work out of the box already for structs and enums as long as Solidity >=0.8.20 is used. `@param` is still not supported. Solidity continues to be the limitation...

Exposing return parameters is a good idea. `astNode` is a `private` TypeScript variable but you should still be able to access it in your Handlebars templates. Can you try that...

This is great @tzapu! I just had an idea: it would be nice to feature example templates in the readme. Do you want to create a PR adding an "Example...

What information about override do you think should be exposed? Just that a function is an override?