Generate multiple swagger-files about apipie-rails HOT 7 CLOSED

@PanosCodes Since you've rebuilt the whole Swagger implementation... Do you have any pointer?

Do we need to a config setting to maintain backward compatibility?

from apipie-rails.

I think it might be simple

• The version part can already be handled by apipie:static_swagger_json rake task, you can pass the version you want to output for example bundle exec rake apipie:static_swagger_json\[2\].

• For the namespace part of the problem, Apipie::Application::to_swagger_json uses Apipie::Generator::Swagger::ResourceDescriptionsCollection#filter to filter 😅 the resources for output so maybe there is an elegant way to extend that.

It seems like it can be implemented without any breaking changes.

from apipie-rails.

I will investigate it more tomorrow 🙂
But then it feels like it would be easiest to fix by handling it via rake-commands instead of the config?

from apipie-rails.

Correct, I don't think the configuration is the right place for that.

from apipie-rails.

Thanks for the update

from apipie-rails.

@PanosCodes It seems like no matter which version I generate, they all end up in the same file and overwrite each other.
Am I missing some configuration?

from apipie-rails.

Decided to add my namespace to the version and use the ENV["OUT"]:

OUT=./swagger/v1/namespace_a bundle exec rails apipie:static_swagger_json\[1\.namespace\_a\]
OUT=./swagger/v1/namespace_b bundle exec rails apipie:static_swagger_json\[1\.namespace\_b\]

from apipie-rails.