Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow configuration of YAML output format through config #14

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

MarcEspiard
Copy link

Description

Adds an option to control the inline and indent of the yaml output through config

Motivation and context

Useful for readability of exported yaml file, especially during development of the api when you might not have a solution yet to display the docs in an actual frontend.
It is also coherent with the json output format using the JSON_PRETTY_PRINT flag, this PR allows you to pretty print the YAML file if you wish to do so.
It is backward compatible with default values not changing behavior for existing installs

How has this been tested?

Tested the output while changing config values, all works as expected

Screenshots (if appropriate)

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

  • I have read the CONTRIBUTING document.
  • My pull request addresses exactly one patch/feature.
  • I have created a branch for this patch/feature.
  • Each individual commit in the pull request is meaningful.
  • I have added tests to cover my changes.
  • If my change requires a change to the documentation, I have updated it accordingly.

If you're unsure about any of these, don't hesitate to ask. We're here to help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants