Closed bademux closed 8 years ago
You can contribute back or find an alternative. I'm not making you use the code, and that attitude isn't very OSS friendly
Looks like a lot of things are unfixable without breaking compatibility. It is better to cooperate for fixing where it possible (or plan breaking fixes for further release) , then take offense by closing the issue.
It's really simple. If you have constructive input, an issue is good. If you have contributions, a pull request is good. If you propose breaking compatibility then a conversation is good. But if you want to complain just to complain, use your diary instead of this github project
Please. ask to the first 4 points. I'm simply don't understand 1.why parser library downloads json\yaml
For item, 1:
https://github.com/swagger-api/swagger-parser#overview
This project's goal is to download definitions, validate and return POJOs. To do that, because of relative and remote references, it needs to read references, which may be JSON, YAML, and authenticated.
For item 2:
Yes, but like all libraries, you should deprecate existing, old APIs and it requires a version bump.
For item 3:
I don't know what the question is
For item 4:
There is an issue with Mokito implementation in that test.
The whole code base as well as project itself (java part) lacks of review and.
Suggesting to run findbug or just IntelliJ Idea Analyzer (~30 000 warnings and errors), from stupid like public static enum
to serious like if (str == "")
.
Trying to use it in my project (firstly attempt to use swagger-codegen, but it just a mess).