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
Right now we support match as a function but it only operates on the path. Might be cool to switch that (or otherwise support) matching on the whole request summary object ({ url, query } etc.):
This could enable more complex matching logic that depends on different parts of the request to cohere, or conditionally matches some parts of the request based on others.
It would be cool if you could either return explicit boolean true/false, or else either throw or return undefined, similar to how existing match functions work inside match-deep - maybe we would use match-deep to process internally, just pass it the request summary object instead of only the url.
Right now we support match as a function but it only operates on the path. Might be cool to switch that (or otherwise support) matching on the whole request summary object (
{ url, query }
etc.):This could enable more complex matching logic that depends on different parts of the request to cohere, or conditionally matches some parts of the request based on others.
It would be cool if you could either return explicit boolean
true
/false
, or else either throw or returnundefined
, similar to how existing match functions work insidematch-deep
- maybe we would usematch-deep
to process internally, just pass it the request summary object instead of only theurl
.Relates to #441.
The text was updated successfully, but these errors were encountered: