Hey James,
I'm trying to raise a PR (from
https://bitbucket.org/tom_akehurst/swagger-request-validator) to add the
missing parameter constraints, but I'm getting 500s from Bitbucket. Any
idea what's happening?
Cheers,
Tom
On Tuesday, September 27, 2016 at 8:34:39 AM UTC+1, Tom
find the time this week to look at it.
>
> Finally, any objection to me bumping up to the latest WireMock version
>> while I'm at it?
>
>
> None at all.
>
> Cheers,
>
> James
>
> On Monday, September 26, 2016 at 11:47:56 PM UTC+10, Tom Akehurst wrote:
&
ssues you find on the issue tracker attached to
> the repo.
>
> On Tuesday, September 20, 2016 at 9:08:10 PM UTC+10, Tom Akehurst wrote:
>>
>> Hello!
>>
>> I'm trying to find a good way to implement the following use case:
>> I'm building a WireMock-base
and
> also the definitions are a *subset* of JSON schema. Please take a look
> here for all the gory details:
>
> https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md
>
> On Sep 20, 2016, at 8:54 AM, Tom Akehurst >
> wrote:
>
> Haha, showing my ignora
Haha, showing my ignorance here. Hadn't realised that the definitions part
of a Swagger doc was actually JSON schema.
On Tuesday, September 20, 2016 at 4:49:37 PM UTC+1, tony tam wrote:
>
> What do you mean?
>
> On Sep 20, 2016, at 8:48 AM, Tom Akehurst >
> wrote:
>
&
Is there a way to adapt a Swagger spec to JSON schema?
On Tuesday, September 20, 2016 at 3:38:03 PM UTC+1, Max Goldstein wrote:
>
> Not only is the inflector tied to a specific stack, it seems to not be
> feature-complete. My best idea is to validate incoming requests (and
> outgoing responses)
Hello!
I'm trying to find a good way to implement the following use case:
I'm building a WireMock-based mock of a 3rd party API my project depends
on. I'd like to be able to write a suite of tests that can be run against
either the real API or the mock, where each HTTP request/response is
captu
