Is private(set) really desirable?

[uber]

Is private(set) really desirable?

[elsh]

Reset is a great idea, but in this case, it actually takes less bookkeeping (thus simpler) to configure setting vars directly via an input flag. See if https://github.com/uber/mockolo/releases/tag/1.3.1 resolves your scenario. If needed we can revisit a reset function in the future.

[FranzBusch]

A method to reset the mock sounds reasonable and even better than manually zeroing the counts.

[elsh]

We can make it configurable. How soon would you need this? Also feel free to push a PR if possible. Our ETA is within the next couple of weeks.

[FranzBusch]

@elsh not super critical for us right now. We just quickly changed the code that was making use of this.

I would like to understand the reasoning why making it private in the first place is desirable.

[marciniwanicki]

I think private(set) might be quite useful to ensure the internal mock state is not accidentally tempered by the tests. If the mock needs to be reused or brought to the initial state, a resetMock() (or similar) method could be an alternative to ensure all of the properties are getting into the initial state.

[FranzBusch]

@elsh Thanks a lot for the quick help here! Really appreciated