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

multi config support (v2.0) #40

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

Conversation

Sano000
Copy link
Contributor

@Sano000 Sano000 commented Jun 15, 2015

Hi, here is a multi API support (v2.0 for Laravel 5).

Each API configuration should be in a separate file, format is like in swaggerel.php now. You have to add an "additional" parameter to swagervel.php config file. There should be relative (in Laravel format) paths pointed to new configs:

...
    'additional' => [
        'swaggervel.api1', // config/swaggervel/api1.php
        'swaggervel.api2', // config/swaggervel/api2.php
        'swaggervel.api3', // config/swaggervel/api3.php
    ]
...

A new "api-docs-route" and "active" options was added.

_How it works_

Different API controllers are stored in different paths:

app/controllers/json/api1
app/controllers/json/api2
app/controllers/json/api3

You need to add 3 config files into app/config/ or config subdirectory:

api1.php
api2.php
api3.php

Config file format is the same as before, but need to exclude other APIs using 'excludes' param. For example, api1.php:

...
    "excludes" => array(
        app_path()."/storage",
        app_path()."/tests",
        app_path()."/views",

        app_path()."/controllers/json/api2",
        app_path()."/controllers/json/api3",
    ),
...

Another bugfix with an annotations file extention. It is failing when "resourcePath" of @swg\Resource has a dot inside.

@Sano000 Sano000 changed the title multi config support multi config support (v2.0) Jun 15, 2015
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.

1 participant