-
Notifications
You must be signed in to change notification settings - Fork 12
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
Cassette config inheritance #153
Conversation
Codecov Report
@@ Coverage Diff @@
## master #153 +/- ##
=========================================
+ Coverage 73.9% 75.51% +1.6%
=========================================
Files 36 36
Lines 1506 1511 +5
=========================================
+ Hits 1113 1141 +28
+ Misses 393 370 -23
Continue to review full report at Codecov.
|
All looks good, except: We should update the parameter docs for |
And document - make it explicit that any parameters set in |
Cool, I'll work on updating the docs. |
I took a stab at documenting the new inheritance behavior in |
looks good to me - can you resolve the conflict, then i can merge |
Cassette options defined in vcr_configuration() were ignored by `insert_cassette()` and `use_cassette()` in favor of their defined argument defaults.
- make it clearer that wrapping ... in curly braces is not required - remove outdated message about recording modes being supported in the future
6d033a7
to
42309cf
Compare
Thanks for looking it over. I made a few additional non-coding changes that include some minor rewording/reorgs in the docs. Suggesting looking over
Also just rebased to sync up with master. |
Both look good, thanks. |
Resolved by ropensci/vcr#153
Resolved by ropensci/vcr#153
As discussed in #151. This changes the defaults for arguments in
use_cassette()
/insert_cassette()
toNULL
if they control parameters that are also configurable viaVCRConfig
. Before making this change I reformatted the code so there's only one argument per line to make the diff more readable.Other changes:
vcr_test_configuration()
to reset the current configuration and restore settings that should be in place for all tests. This could be called within ateardown()
block at the top of every test file that includes modifications to the configuration. Currently it's only used in the new inheritance tests.vcr_configuration()