Apply assertions to VCRConfig's initial arguments #156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is mostly an academic change with zero functional impact for users but I think it's the "correct" approach for adding assertions to R6 classes, so it might be useful as a reference if nothing else.
In the current implementation assertions are only applied when updating the fields of an existing object, so it's possible to initialize an object with an invalid value:
With this new change, initial arguments are passed to the active binding rather than being assigned directly to their private field, so assertions are applied in both cases:
Created on 2020-02-19 by the reprex package (v0.3.0)
You have way more experience with R6 so I'm curious to see what you think and whether I'm missing something.