Example doesn't work, throws error on swagger document. about swagger-tools

[whitlockjc]

I fixed this a few hours ago in commit 692d058. I just tested it to verify things are working as expected.

[avishaan]

Oh lol, I just figured it out by logging the entire error to the console. For errors it might be better in the example to log the entire error. Especially for those of us just getting started on this.

[whitlockjc]

What caused this is the upstream schema changed the type of swagger from Number to String. I could add a --verbose flag to the CLI to let you see all parts of the error. What do you think?

[theganyo]

I noticed this the other day w/ a127 verify. I think it probably always needs to include the path or the message isn't very useful.

[whitlockjc]

The path is there, as a JSON Pointer. That's what the #/swagger part of the output is.

[theganyo]

Ah. Gotcha. When it's for the "swagger" element and just says "swagger" it's not clear. :)

[whitlockjc]

I'm open to suggestions. The idea was to use some sort of standard for pointing to a particular place in a JSON document and that's why I chose the syntax I did. It's not set in stone by any means but it does seem like a pretty reasonable approach.

[theganyo]

No, it makes total sense! It's only a bit problematic when the path is "/swagger". Which, in general, should be close to never.

[whitlockjc]

Hahaha! Yeah, I agree. When it's short like that it's unintuitive. If you have any suggestions on how we might fix this, let me know.