-
Notifications
You must be signed in to change notification settings - Fork 70
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
Schema references #7
Comments
This is a cool idea! Open to any suggestions on how you'd implement this |
Maybe start the parsing on models... definitions based on models. But some definitions doesn't have models, but if I need to create some unused models, it's acceptable deal for me to create a full & nice documentation. |
For example something like this:
This format is based on docBlock, and give information about field types too.
In this case the swagger definition is based on docBlock and if I miss something to document there it will not show in the final documentation. |
In my documentation what I created by hand I use
definitions
like this:Here are the definitions to this above example:
It would be nice if the laravel-swagger could be generate this definitions because it's a very useful part of the API documentation when the frontend developers thinking about their models.
The text was updated successfully, but these errors were encountered: