Paweł Adamski

Hi @emaccaull I will have a look on it.

I guess you mean JSON path :) HttpClientMock in current version works fine with `json-matchers` ``` HttpClientMock mock = new HttpClientMock(); mock.onGet("/aaa").withBody(isJsonStringMatching( jsonObject().where("foo", is(jsonInt(1))) ) ); ``` Do you need...

Hi @jarst Thanks for contributing to HttpClientMock. I've looked at your PR. I agree that adding dependency is not a big improvement. TBH I rather thought about adding a method...

Hi @ipichris Thanks for finding that issues. I will try to look on it during the weekend.

Using HttpClientResponseBuilder in the way as you presented is not possible because it contains a definition of all the rules and actions. So if you would pass it to verify...

Hi @Priyanshu-ai902 I'm happy to hear that you are interested in contributing to HttpClientMock. Feel free to work on HttpAsycClient.It would be great if you could first expalin my your...

@Priyanshu-ai902 Your code doesn't give me enough information how you would like build mock for HttpClientAsync. Please provide more detail or working examples.

Thanks @booniepepper for nice words about the project. I'm happy to hear that you enjoy using it. We are now in the process of migration all our projects to Xebia...

Why do you think it is a big change? I see it rather small, `equals` and `hashcode` are very simple and can be even generated automatically. I'm writing a library...