Anders D. Johnson

Starting to pull in the `webextension-polyfill` to help support Firefox and other browsers in future. We'll have to switch up some of the code to import `browser` and access the...

Allow mocks to export an object syntax instead of nested arrays (and let `mockyeah.get()`, etc. accept these as a single argument), e.g.: ```js { match: 'http://example.com', options: { text: 'ok'...

Support (or test if already support) loading suites from file as plain JSON files. This will enable/support #412 as well. For regex instead of strings we could consider `{ path:...

We could support dynamic record groups (like in #252) but per-recording as options. This would be useful for programmatic use, but maybe not CLI (expect perhaps as `--group label:regex/pattern`). Also...

Similar to how `.expect({ ... })` and `.expect().query({ ... })` can take match objects, we should support a new `.headers({ ... })` in addition to current support for name/value pairs...

We could support raw `RegExp` instances (or `{ "$regex": "a.*b" }`), and even functions, in the `only` record options, and in the `groups` config. Relates to #274 and #276.

Config groups for recording should support full match objects to specify which requests are recorded. This would give full parity with the API for mocks. We would support a limited...

Add support for mocking GraphQL queries. Match on query arguments from an object. Have to think about the API - maybe something like this: ```js mockyeah.mock({ graphql: { query: 'human',...

Jest seems to be in vogue now over mocha, and supports mocking in more seamless way than mocha or addons to it, which would come in handy for unit tests...