Feature request: Possibility to specify baseUrlPath in the code about express-oas-generator HOT 7 CLOSED

I think I might have resolved this myself. I found this workaround and it works very well for me:

expressOasGenerator.init(app, function(spec) {
    spec.basePath = process.env.BASE_URL || '';
    return spec;
});

Please feel free to close this ticket if you think that this is a good solution.

from express-oas-generator.

Actually there is a possibility to specify baseUrlPath but looks like it is not propagated to the actual specification here.
Would you, @adams-family , be so kind to add a line, check tests and create a PR?

from express-oas-generator.

And thank you for promotion!

from express-oas-generator.

Hi @adams-family, I implemented the "feature" could you try it and let me know if it works as expected? I can publish new version after it.

from express-oas-generator.

Hi @mpashkovskiy - I'm sorry I missed your original message a month ago :(

In my case, specifying the baseUrlPath in the package.json is not ideal because I'm running a monorepo (nrwl.io) and I have multiple NodeJS project covered by one package.json. Each project is deployed to a different baseUrl on the same host, such as:

• /public-api
• /admin-api

I am however happy with the workaround I found (above) because this way I can specify a different baseUrl per each project:

expressOasGenerator.init(app, function(spec) {
    spec.basePath = process.env.BASE_URL || '';
    return spec;
});

Is there anything else I can test for you?

from express-oas-generator.

I see. Indeed my implementation won't be useful for you. Thanks for explanation, no actions needed then.

from express-oas-generator.

No worries, thanks again for this great tool!

from express-oas-generator.