Closed mgravell closed 7 months ago
Sooooooo I think I missed this because interval isn't in there either…
Thoughts on some reflection-based test for clone checking to prevent future misses?
Sooooooo I think I missed this because interval isn't in there either…
added; I have no great ideas on the reflection thing - feel free to suggest
maybe just a count of the fields on ConfigurationOptions
with a known expected value:
Assert.Equals(43, fields.Length); // if this fails, check Clone() has been updated
+1 I like it - simple and effective we can get fancier if ever justified. Do you mind adding in this PR please? If slammed I can follow-up later in day too.
@NickCraver already working on it
release 2.7.23 added a
ConfigurationOptions.HeartbeatConsistencyChecks
option, but that option is not represented inClone()
; fix that