You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 subset with at least matches in static JSON config (the same subset supported in #414 - and maybe regex too if we solve #276 or with { path: { "$regex": "a.*b" } }), full features with programmatic use, and maybe also some limited support with CLI args for dynamic groups (#274).
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 subset with at least matches in static JSON config (the same subset supported in #414 - and maybe regex too if we solve #276 or with
{ path: { "$regex": "a.*b" } }
), full features with programmatic use, and maybe also some limited support with CLI args for dynamic groups (#274).So we could write the following:
The text was updated successfully, but these errors were encountered: