Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ivan Goncharov
    @IvanGoncharov
    It will be pure-JS starting from now on.
    We still working on browserify version.
    Khanh Nguyen
    @knguyen6
    Hi guys, I'm kind of a noob here. So I npm installed the api-spec inverter. Copy-paste the command line example: api-spec-converter <my json file name> --from type_1 --to type_2 > output_spec but it said -bash: api-spec-converter: command not found
    Ivan Goncharov
    @IvanGoncharov
    Did you install it globally?
    like npm install -g api-spec-converter
    if not try node_modules/.bin/api-spec-converter
    Or you can try to use our online demo http://lucybot.github.io/api-spec-converter
    Khanh Nguyen
    @knguyen6
    I ran node_modules/.bin/api-spec-converter in the command line, does it suppose to do something ? (I'm sorry if my questions seem dumb, I'm real noob at this swagger thing)
    Ivan Goncharov
    @IvanGoncharov
    If it doesn't produce: api-spec-converter: command not found
    that mean you install it locally
    so node_modules/.bin/api-spec-converter <my json file name> --from type_1 --to type_2 > output_spec
    is a way to go
    or you can install it globally with npm install -g api-spec-converter
    to remove node_modules/.bin/ prefix
    Khanh Nguyen
    @knguyen6
    Thank you, no more command not found error :)
    Ivan Goncharov
    @IvanGoncharov
    it specific of NPM if you install without -g it puts executables in node_modules/.bin/
    Morgan Courbet
    @nagromc
    Hi guys, I've opened an issue (#83) on the GitHub repo, and version 1.8.0 doesn't seem to be affected by the error I came across. Great! But, at this time, version 1.8.0 is only published on Bower, but not on npm. Is it planned to publish v 1.8.0 on npm soon? :smile:
    Ivan Goncharov
    @IvanGoncharov
    Sorry it was my mistake
    I tried new system with Travis publishing to NPM
    I will release package in couple hours
    Thank you for reporting
    Morgan Courbet
    @nagromc
    Great! Thank you very much again @IvanGoncharov :+1:
    Ivan Goncharov
    @IvanGoncharov
    I released 1.8
    it took me multiple tries to figure out how to do this, Tavis has very basic documentation :(
    Morgan Courbet
    @nagromc
    Thanks @IvanGoncharov you're awesome!
    lollo
    @FreeLollo_twitter
    hello
    fuck
    Guillaume Mantopoulos
    @MrGuiMan
    Hi everyone
    Bobby Brennan
    @bobby-brennan
    Hi Guillaume, just saw your issue on api-spec-converter, taking a look now
    Guillaume Mantopoulos
    @MrGuiMan
    thanks
    Bobby Brennan
    @bobby-brennan
    Looks good overall. The only issue I see is that you've changed it to only look at the first MIME type
    so if the first MIME type is unknown, but the second MIME type is application/json or something we know about, it'll get dropped
    Guillaume Mantopoulos
    @MrGuiMan
    right
    should we maintain a list of “supported” MIME types in an array and loop through content to get the first available one ?
    Bobby Brennan
    @bobby-brennan
    that seems like a good solution
    Guillaume Mantopoulos
    @MrGuiMan
    i’ll get on that asap and create a pull request towards the main repo
    Bobby Brennan
    @bobby-brennan
    awesome thanks!
    Guillaume Mantopoulos
    @MrGuiMan
    done
    although travis did not seem to like Object.values
    Guillaume Mantopoulos
    @MrGuiMan
    @bobby-brennan PR has been fixed
    Bobby Brennan
    @bobby-brennan
    Thanks Guillaume, merged && published
    Guillaume Mantopoulos
    @MrGuiMan
    Cool ! Thank you
    I might look into the placeholders stuff, just unsure how to pass the option in yet
    Bobby Brennan
    @bobby-brennan
    Sounds good. FYI, here's the CLI logic
    Jimmy Shiau
    @jimmyshiau
    how to use --dummy in command line?
    any example?
    Bobby Brennan
    @bobby-brennan
    api-spec-converter --from=swagger_1 --to=swagger_2 --dummy https://raw.githubusercontent.com/LucyBot-Inc/api-spec-converter/master/test/input/swagger_1/petstore/pet.json > swagger.json
    Kevin Kaland
    @wizonesolutions
    Seems like the WADL converter doesn't actually convert WADL representations...it just adds some placeholders. Unfortunately, this means I get no return values when subsequently generating an API client from the Swagger 2.0 spec (since it doesn't output a produces key). I'm trying to use Node to fix this, but maybe it's easiest to just fix it in source on my fork? Gonna try that before I give up on generation, haha.
    namely this part, which doesn't "take responses from the WADL file" https://github.com/LucyBot-Inc/api-spec-converter/blob/master/lib/formats/wadl.js#L165-L174
    Kevin Kaland
    @wizonesolutions
    Fixed it, but it didn't solve my underlying issue anyway since I'm not sure how I would convert models. I guess I could find an XSD-to-JSON conversion lib and try to manually fix up the file, but at this point I'll just write my client library by hand :)