VCR.py should be OAuth-timestamp / nonce agnostic about vcrpy HOT 6 CLOSED

I would like to add support for custom request matchers. This would allow you to register a function that takes two Request objects, and returns True if they match, False if they don't. I think this would solve this issue.

I have an API already for registering custom serializers, I would like to use the same registration mechanism.

from vcrpy.

Actually, providing a mode where it just matches on request path + method, and ignoring body contents for matching purposes, might solve this problem as well?

from vcrpy.

Regarding your first message:

Aye, that's a great idea: it throws the ball into the user's court. In my case, I would still need to parse the request and strip out the parameters.

About request path + method: yes, this is actually fine. This feels like we're moving towards HTTPretty — VCR. TBH I'd love to see these two projects eventually converge... haha. HTTPretty with recording/playback features would be great (EDIT: ah, well, I just saw this. Always ahead of the game, aren't you!)

So yes; when recording, record everything but when looking up responses just match on request path and method.

How would you implement this?

from vcrpy.

Just implemented it, check out the staging branch and let me know if that works for you :)

from vcrpy.

I went ahead and released the new request-matching framework, I think this should solve this issue.

from vcrpy.

I will give it a shot... that was very quick!

from vcrpy.