-
Notifications
You must be signed in to change notification settings - Fork 34
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
Support setting directories for property 'swaggerInput' #41
Comments
Would you like to contribute this functionality? |
I work with open-source extensively, mostly on GitHub. Hence, I half-expected this to be the first initial comment 😜 I'm thinking about it as I definitely have to implement this functionality anyhow. |
😁👍 |
@RobWin it'd be helpful if you could give me an indication whether the PR meets your expectations. And if so, in what time frame can you image merging it to release a new version? That would allow us to assess whether we need to temporarily deploy my fork for the time being. |
Thx. Could you please add a test to show what happens when two Swagger files (swagger1.json and swagger2.json) reside in the same folder like |
Good point, that use case is currently not supported (i.e. markdown files would get overwritten).
Yes, something like that - but only if there really are multiple files in the same folder. Otherwise the directory structure in the output dir is too deeply nested. I'll take a stab at it later today. |
The tests |
The code seems to generate a strange URI:
|
Sorry, had to get a hold of a Windows environment first. I'm glad you seem to have tried to release from a Windows box otherwise this bug would likely have slipped through. |
V1.3.4 has been released. Would you like to verify that it works. |
Indeed, you released from the "wrong" revision. https://github.com/Swagger2Markup/swagger2markup-maven-plugin/releases/tag/v1.3.4 shows that there are "3 commits to master since this release" with one of which being the essential fix. |
The release contains the commits. I tagged too early. I corrected it. |
It's rather limiting that
swaggerInput
cannot be the path to a folder that contains Swagger files. True, the plugin can be configured multiple times as a workaround but that's really ugly.Ideally I could set a directory for
swaggerInput
and have the plugin deep-scan it for Swagger files.The text was updated successfully, but these errors were encountered: