-
Notifications
You must be signed in to change notification settings - Fork 25
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
Can we integrate SWAGGER into it #22
Comments
Yeah, I think so.. |
Yes, I had done it in my last project. |
Hello @panbhatt I think Swagger would be a great integration. Fork this repository and make your changes from a new branch created off of 'master'. When you're ready to share your changes open a pull request. Thank you for your interest in contributing! Let me know if you need any other assistance. |
#23 |
As per the latest build, npm run lint is failing. and giving error that Fastify is never being used. import * as FastifySwagger from 'fastify-swagger' we have two Options npm run lint pass : (this is a known problem in typescript-eslint-parser). Please suggest what you thing is the most optimal way and I will go by that. |
@Ethan-Arrowood : Any update for me which way you want it to go. |
Tricky question @panbhatt I'm going to look into this and try to figure it out. I'll get back to you soon |
Okay I found a solution, check out the review comments I left on your PR. More feedback coming soon too! |
* Fastify Swagger implementaion has been done with Matterhorn. Swagger interface will be available on the same port as that of Main Application with a path /documentation E.g. http://localhost:3000/documentation A sample path /user/{id} has been created where a user can post a Object (user creation object as per the schema )and corresponding result will be returned. * Adding the LINTING RULES. * Added changes to make sure the tests are passing. * Adding a new test case for #22 Issue. * Adding back the properties required for Swagger documentation. Removing extra fields from test.ts * Changed Version of fastify-swagger to 2.3.2 to reduce the warnings of using unrelated properties in the schema. * Adding the changes as suggested by ETHAN. /* eslint-disable-next-line no-unused-vars */ * Added some more changes as suggested by Ethan. POST block is moved to configureSwaggerPlugin. * update package-lock * Closer to fixing the coverage ci issue * solved issue * fix spelling mistake
Can we integrate SWAGGER into it
The text was updated successfully, but these errors were encountered: