Hi,

It seems like the HTTP Assert package does not allow me to specify a body to pass in a POST request for example. Looking at the HTTPBody() function, the body argument is set to nil:
req, err := http.NewRequest(method, url+"?"+values.Encode(), nil)

Is this by design, or am I looking at a missing feature?

Cheers,

It may help in some cases of debugging to see what is the registered worker's scope. I don't think there's a way to see the worker's scope in the DevTools, it only lists "clients".

[MSW] Mocking enabled.
- Documentation: https://mswjs.io/docs
- Find an issue? <GITHUB_LINK>
- Scope: /

We may also consider printing additional information:

• The worker script location;
• The list

Issue

The response header does not reflect the correct version for HTTP2 requests. Even though, wiremock replies in h2 but the version in the response header shows "HTTP/1.1 200". This is caused by the hardcoded value in the toString() method of Response.java class

    @Override
    public String toString() {
        StringBuilder sb = new StringBuilder();
        **sb.append("HTTP

Hey Guys,
I see an IllegalStateException when running one particular test.

What steps will reproduce the problem?
The following code fails each time it is run

Testcase:

package backend.model.posting

import backend.controller.exceptions.ConflictException
import backend.model.location.Location
import backend.model.user.UserAccount
import org.junit.Before
import org.

https://github.com/agriffis/vcrpy-unittest adds a VCRTestCase (and a VCRMixin) class. They consists only of 23 lines of code. Please include those two functions in your project to avoid needing to install another package. Those tiny package have a bigger overhead and packaging them for Debian would be rejected due to this reason.

The issue is based on the discussion in #559.

@zvirja

should we probably modify CI so that doc is published automatically on push to master? This way if we don't want doc to be released right now - just keep it in a branch. Otherwise, we have this non-synchronized docs and manual work.. 😟

@dtchepak

I'm not sure what to do about publishing docs. It would be nice to auto-publish,

Take this class, for example:

`
import Foundation

// some comment has import SOMEBADTHING
public protocol TestProtocol: AnyObject {
func doSomething() -> Void
}
`

The generated mock ends up having:

... import SOMEBADTHING ...

Looks like it is looking for "{import .*}" in source files and just adding that verbatim to the output file, causing compile issues.