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 for tsoa config to use yaml #133
Labels
Comments
isman-usoh
added a commit
to isman-usoh/tsoa
that referenced
this issue
Jul 20, 2017
- support `tsoa swagger -c tsoa.yaml` yaml config file lukeautry#133 - support `tsoa swagger --yaml` output yaml format
isman-usoh
added a commit
to isman-usoh/tsoa
that referenced
this issue
Jul 21, 2017
- support `tsoa swagger -c tsoa.yaml` yaml config file lukeautry#133 - support `tsoa swagger --yaml` output yaml format
10 tasks
isman-usoh
added a commit
that referenced
this issue
Jul 27, 2017
- Support Query array type - Support custom response header (#89) - Support tsoa config yaml format (#133) - Support generate swagger yaml format - Support string, number and boolan UnionType (#5) - Support AnyKeyword (#114) - update route schema and update type - Change swagger enum inline type to enum definitions - Add new rule for tslint - Fix set status not work #94 - Fix validate - Set query array collectionFormat, default to multi - Create file for Circle CI
isman-usoh
added a commit
that referenced
this issue
Jul 27, 2017
- Support Query array type - Support custom response header (#89) - Support tsoa config yaml format (#133) - Support generate swagger yaml format - Support string, number and boolan UnionType (#5) - Support AnyKeyword (#114) - update route schema and update type - Change swagger enum inline type to enum definitions - Add new rule for tslint - Fix set status not work #94 - Fix validate - Set query array collectionFormat, default to multi - Create file for Circle CI
Fix: 0534cbd |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're currently trying to add some more detailed documentation to our swagger description and experiencing the pain that is no multi line strings in json. Would the team be open to allowing yaml config files? I would be happy to contribute.
The text was updated successfully, but these errors were encountered: