Closed pradovic closed 5 years ago
Hi @pradovic
This is intended and this is why it's 2.x. You can use myMock.Set() instead of direct assignment to InsertFunc which is now private due to some internal mechanics. Mock generation goes much faster bc there's no type checking involved in 2.x version and this is also intended.
If for some reason you're not ready to switch to 2.x you can download 1.9.x binaries from the releases page.
When I generate mocks using new version of minimock, all the functions are missing, and my old tests get compilation error, for ex: myMock.InsertFunc undefined. Is this intended or am I doing something wrong maybe? Also, mock generation goes much faster then before.