matcher

Expected Behavior

Invoking a mockk should never cause a test to hang. If too many invocations lead to performance issues, it would be better to either:

• throw an exception once a reasonable cap is reached
• rotate away old data

Current Behavior

After invoking a mock around 130 000 times (on my machine, running JDK 15 on Windows) further invocations will hit a wall and take for

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.

Although the two source streams and the result stream have all a length of 5, an exception is thrown.

Reproduction:

import { cold, hot } from 'jest-marbles'
import { buffer, mergeAll } from 'rxjs/operators'

describe('test', () => {
  it('should not fail', () => {
    const source1 = cold('AB--|')
    const source2 = hot('^-A-|')
    expect(source1.pipe(buffer(source2), mergeAl

Feature Request

Parse all bodies as a Buffer and only looks at requests where the Content-Type header matches the type option. This parser supports automatic inflation of gzip and deflate encodings.