Download the PHP package d-scribe/laravel-apidoc-generator without Composer
On this page you can find all versions of the php package d-scribe/laravel-apidoc-generator. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download d-scribe/laravel-apidoc-generator
More information about d-scribe/laravel-apidoc-generator
Files in d-scribe/laravel-apidoc-generator
Package laravel-apidoc-generator
Short Description Generate beautiful API documentation from your Laravel application
License MIT
Homepage http://github.com/ezra-obiwale/laravel-apidoc-generator
Informations about the package laravel-apidoc-generator
This package is abandoned and no longer maintained. Please use the knuckleswtf/scribe package instead.
Laravel API Documentation Generator
Automatically generate your API documentation from your existing Laravel/Lumen/Dingo routes. Here's what the output looks like.
php artisan apidoc:generate
Note: this is the documentation for version 3, which changes significantly from version 2. if you're on v2, you can check out its documentation here. We strongly recommend you upgrade, though, as v3 is more robust and fixes a lot of the problems with v2.
Installation
Note: PHP 7 and Laravel 5.5 or higher are required.
Laravel
Publish the config file by running:
This will create an apidoc.php
file in your config
folder.
Lumen
-
Register the service provider in your
bootstrap/app.php
: - Copy the config file from
vendor/d-scribe/laravel-apidoc-generator/config/apidoc.php
to your project asconfig/apidoc.php
. Then add to yourbootstrap/app.php
:
Usage
Before you can generate your documentation, you'll need to configure a few things in your config/apidoc.php
.
url
This is the url to show in the request examples. It is also used in the postman collection. Set this with DOCUMENTATION_URL in the.env
file otherwise it defaults to APP_URL.-
output
This is the file path where the generated documentation will be written to. Default: public/docs -
postman
This package can automatically generate a Postman collection for your routes, along with the documentation. This section is where you can configure (or disable) that. -
router
The router to use when processing the route (can be Laravel or Dingo. Defaults to Laravel) -
logo
You can specify your custom logo to be used on the generated documentation. Set thelogo
option to an absolute path pointing to your logo file. routes
This is where you specify what rules documentation should be generated for. You specify routes to be parsed by defining conditions that the routes should meet and rules that should be applied when generating documentation. These conditions and rules are specified in groups, allowing you to apply different rules to different routes.
For instance, suppose your configuration looks like this:
This means documentation will be generated for routes in all domains ('*' is a wildcard meaning 'any character') which match any of the patterns 'api/*' or 'v2-api/*', excluding the 'users.create' route and any routes whose names begin with admin.
, and including the 'users.index' route and any routes whose names begin with healthcheck.
. (The versions
key is ignored unless you are using Dingo router).
Also, in the generated documentation, these routes will have the header 'Authorization: Bearer: {token}' added to the example requests.
You can also separate routes into groups to apply different rules to them:
With the configuration above, routes on the v1.*
domain will have the Token
and Version
headers applied, while routes on the v2.*
domain will have the Authorization
and Api-Version
headers applied.
Note: the
include
andexclude
items are arrays of route names. THe * wildcard is supported. Note: If you're using DIngo router, theversions
parameter is required in each route group. This parameter does not support wildcards. Each version must be listed explicitly,
To generate your API documentation, use the apidoc:generate
artisan command.
It will generate documentation using your specified configuration.
Documenting your API
This package uses these resources to generate the API documentation:
Grouping endpoints
This package uses the HTTP controller doc blocks to create a table of contents and show descriptions for your API methods.
Using @group
in a controller doc block creates a Group within the API documentation. All routes handled by that controller will be grouped under this group in the sidebar. The short description after the @group
should be unique to allow anchor tags to navigate to this section. A longer description can be included below. Custom formatting and <aside>
tags are also supported. (see the Documentarian docs)
Note: using
@group
is optional. Ungrouped routes will be placed in a "general" group.
Above each method within the controller you wish to include in your API documentation you should have a doc block. This should include a unique short description as the first entry. An optional second entry can be added with further information. Both descriptions will appear in the API documentation in a different format as shown below.
You can also specify an @group
on a single method to override the group defined at the controller level.
Result:
Specifying request parameters
To specify a list of valid parameters your API route accepts, use the @urlParam
, @bodyParam
and/or @queryParam
annotations.
- The
@urlParam
and@bodyParam
annotations take the name of the parameter, its type, an optional "required" label, and then its description. - The
@queryParam
annotation takes the name of the parameter, an optional "required" label, and then its description
They will be included in the generated documentation text and example requests.
Result:
Note: a random value will be used as the value of each parameter in the example requests. If you'd like to specify an example value, you can do so by adding Example: your-example
to the end of your description. For instance:
Note: You can also add the @bodyParam
annotations to a \Illuminate\Foundation\Http\FormRequest
subclass:
Indicating auth status
You can use the @authenticated
annotation on a method to indicate if the endpoint is authenticated. A "Requires authentication" badge will be added to that route in the generated documentation.
Providing an example response
You can provide an example response for a route. This will be displayed in the examples section. There are several ways of doing this.
@response
You can provide an example response for a route by using the @response
annotation with valid JSON:
Moreover, you can define multiple @response
tags as well as the HTTP status code related to a particular response (if no status code set, 200
will be returned):
@transformer, @transformerCollection, and @transformerModel
You can define the transformer that is used for the result of the route using the @transformer
tag (or @transformerCollection
if the route returns a list). The package will attempt to generate an instance of the model to be transformed using the following steps, stopping at the first successful one:
- Check if there is a
@transformerModel
tag to define the model being transformed. If there is none, use the class of the first parameter to the transformer'stransform()
method. - Get an instance of the model from the Eloquent model factory
- If the parameter is an Eloquent model, load the first from the database.
- Create an instance using
new
.
Finally, it will pass in the model to the transformer and display the result of that as the example response.
For example:
For the first route above, this package will generate a set of two users then pass it through the transformer. For the last two, it will generate a single user and then pass it through the transformer.
Note: for transformer support, you need to install the league/fractal package
@responseFile
For large response bodies, you may want to use a dump of an actual response. You can put this response in a file (as a JSON string) within your Laravel storage directory and link to it. For instance, we can put this response in a file named users.get.json
in storage/responses
:
Then in your controller, link to it by:
The package will parse this response and display in the examples for this route.
Similarly to @response
tag, you can provide multiple @responseFile
tags along with the HTTP status code of the response:
Generating responses automatically
If you don't specify an example response using any of the above means, this package will attempt to get a sample response by making a request to the route (a "response call"). A few things to note about response calls:
- They are done within a database transaction and changes are rolled back afterwards.
- The configuration for response calls is located in the
config/apidoc.php
. They are configured within the['apply']['response_calls']
section for each route group, allowing you to apply different settings for different sets of routes. - By default, response calls are only made for GET routes, but you can configure this. Set the
methods
key to an array of methods or '*' to mean all methods. Leave it as an empty array to turn off response calls for that route group. - Parameters in URLs (example:
/users/{user}
,/orders/{id?}
) will be replaced with '1' by default. You can configure this, however. Put the parameter names (including curly braces and question marks) as the keys and their replacements as the values in thebindings
key. - You can configure environment variables (this is useful so you can prevent external services like notifications from being triggered). By default the APP_ENV is set to 'documentation'. You can add more variables in the
env
key. - By default, the package will generate dummy values for your documented body and query parameters and send in the request. (If you specified example values using
@bodyParam
or@queryParam
, those will be used instead.) You can configure what headers and additional query and parameters should be sent when making the request (theheaders
,query
, andbody
keys respectively).
Class Inheritance and Method Overriding
In the situation where a superclass contains all the route methods and a subclass needs to customize the documentation, each method could be overriden and the docs provided in the annotations like:
OR
the method docs could be added to the class annotations like:
Caveat
- Multi-line isn't possible
Generating based on tags
Sometimes, you may want only a set of endpoints documented, for example, if some endpoints are for internal usage only. Introducing tags
:
Route group tags
Routes may be grouped together and tagged:
Annotation tags
While @hideFromAPIDocumentation
hides all so-tagged methods from the documentation, @tags
allows for a more fine-tuned documentation of methods.
Using tags with command
With either or both of the above tagging methods, you can go ahead to skip internal endpoints by using the --skip-tags
option:
And if you want to generate only internal endpoints, use the --only-tags
options:
Note: Route groups and methods may have multiple tags e.g.
@tags internal important
Note:--skip-tags
and--only-tags
may target multiple tags e.g. `php artisan apidoc:generate --skip-tags=internal,important
Postman collections
The generator automatically creates a Postman collection file, which you can import to use within your Postman app for even simpler API testing and usage.
If you don't want to create a Postman collection, set the postman
config option to false.
Modifying the generated documentation
If you want to modify the content of your generated documentation, go ahead and edit the generated index.md
file.
The default location of this file is: public/docs/source/index.md
.
After editing the markdown file, use the apidoc:rebuild
command to rebuild your documentation as a static HTML file.
You can optional override the output directory with --output=path/to/output
. In the case of rebuilding, documentation must already exist at the location.
If you wish to regenerate your documentation, you can run the generate
command, you can use the force
option to force the re-generation of existing/modified API routes.
Automatically add markdown to the beginning or end of the documentation
If you wish to automatically add the same content to the docs every time you generate, you can add a prepend.md
and/or append.md
file to the source folder, and they will be included above and below the generated documentation.
File locations:
public/docs/source/prepend.md
- Will be added after the front matter and info textpublic/docs/source/append.md
- Will be added at the end of the document.
Further modification
This package uses Documentarian to generate the API documentation. If you want to modify the CSS files of your documentation, or simply want to learn more about what is possible, take a look at the Documentarian guide.
License
The Laravel API Documentation Generator is free software licensed under the MIT license.
All versions of laravel-apidoc-generator with dependencies
fzaninotto/faker Version ~1.8
illuminate/console Version ^5.7|^6.0|^7.0
illuminate/routing Version ^5.7|^6.0|^7.0
illuminate/support Version ^5.7|^6.0|^7.0
mpociot/documentarian Version ^0.4.0
mpociot/reflection-docblock Version ^1.0.1
ramsey/uuid Version ^3.8