andy-maier / ansible-doc-template-extractor

97%

LAST BUILD ON BRANCH main

branch: main

CHANGE BRANCH

x

Reset

• main
• 0.15/andy/fix-required
• 0.15/andy/readme-typo
• andy/add-release-link
• andy/docs-to-rst
• andy/explicit-top-level-parms
• andy/extend-examples
• andy/extend-examples-list-str
• andy/fix-commit-check
• andy/fix-required
• andy/fix-schema-deps
• andy/fix-top-level-array
• andy/generate-exp-example-output
• andy/github-links
• andy/improve-playbook-name-error
• andy/license-pep639
• andy/pattern-properties
• andy/playbook-improvements
• andy/playbook-schema-ref-support
• andy/readme-typo
• andy/remove-schema-desc-2
• andy/sync-rst-md
• andy/test-commit-check
• andy/tests
• andy/to-rst
• andy/tolerate-removed-branch
• andy/type-list
• release_0.15.0
• release_0.15.1
• release_0.16.0
• stable_0.15
• stable_0.16
• start_0.15.1
• start_0.15.2
• start_0.16.0
• start_0.16.1
• start_0.17.0

Build # test-314

Build Type

push

github

Committed by web-flow

Commit Message

Check that top-level element in JSON schemas for input/output is an object (#127)

Details:

* Added a check into the doc templates for playbooks to verify that the
  top-level object described by the schema is an object. That limitation
  is consistent with the spec files for playbooks that define options in
  the spec file and don't use JSON schemas, and consistent with the fact
  that the schema describes a number of variables (each being a property
  on the top-level object).

* Added a function test case for a schema that defines a top-level array
  top make sure the check is in place and works.

Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>

Coverage Stats

276 of 286 relevant lines covered (96.5%)

16.72 hits per line