Felix Fontein

Interestingly this fails in community.general as for some reason, `ansible-doc -l -t filter` does find two documented filters `community.general.lists_mergeby` and `community.general.groupby_as_dict` that `ansible-doc --metadata-dump -t filter` and `ansible-doc -t filter`...

@bcoca is this possibly because the docs are contained in the `.py` file, but the `.py` file is not named the same as the filter?

The current version of the PR shows some differences in the docs build: 1. `apt` module: the `stdout` return variable's `sample` no longer contains newlines 2. `csvfile` lookup: in the...

Changes caused by this PR and its follow-up: 1. The source for the plugin included in the JSON output is no longer the `yml` file with the docs, but the...

Ok, I debugged 3: the problem is that `_list_plugins()` with `content == None` (used for dumping) returns dict keys like `community.dns.community.dns.get_public_suffix`. The code then tries to get the documentation for...

@samdoran should this also be changed for modules? Or should we keep `module: [name]` there? (From a collection maintainer POV, I would suggest to keep the current syntax :) )

It looks like `: ` and `plugin_type: ` are used by ansible-doc in stable-2.9. If both `name:` and `plugin_type:` are not present, it crashes: ``` $ ansible-doc -vvv -t callback...

How about to temporarily (until in, say, 1-2 years) still allow `plugin_type: ` optionally, at least outside ansible-base? I.e. require `name: `, disallow `: `, and allow `plugin_type: ` optionally.

Link to the related analysis by @sivel: https://github.com/ansible/ansible/issues/34595#issuecomment-356091161

[This](https://github.com/ansible/ansible/issues/7005#issuecomment-241096506) seems to be a useful workaround: by writing `block: "{{ foo_block | string }}"` instead of `block: "{{ foo_block }}"`, it no longer fails (at least for me). @etam...