Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

expiry: different options #8

Open
sckott opened this issue Mar 27, 2020 · 0 comments
Open

expiry: different options #8

sckott opened this issue Mar 27, 2020 · 0 comments
Labels
expire request expiration related issues

Comments

@sckott
Copy link
Owner

sckott commented Mar 27, 2020

right now the only way expire time works is across all stubbed/cached requests, that is, if an expire time is set, then on the next http request using webmiddens, all stubs are deleted that are expired

i imagine more fine grained control may be useful:

  • set expire time for all http requests matching a given http request pattern - i guess via any of the webmockr options, e.g., a url pattern, or a header pattern, or a body pattern
  • a user of a package foobar may want to set different expire times for each function of a package they're using, e.g. 10 sec for fxn1(), 1 minute for fxn2(), and 1 week for fxn3()
  • what else?
@sckott sckott added the expire request expiration related issues label Mar 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
expire request expiration related issues
Projects
None yet
Development

No branches or pull requests

1 participant