From ba0fbe9561cdff79d29330dbbe83a146ee35deef Mon Sep 17 00:00:00 2001 From: Landon Clipp <11232769+LandonTClipp@users.noreply.github.com> Date: Sun, 23 Jun 2024 21:48:49 -0600 Subject: [PATCH] Update README.md --- README.md | 23 ----------------------- 1 file changed, 23 deletions(-) diff --git a/README.md b/README.md index 7249166d..bf62b714 100644 --- a/README.md +++ b/README.md @@ -26,29 +26,6 @@ $ task test task: [test] go test -v -coverprofile=coverage.txt ./... ``` -Development Efforts -------------------- - -### v1 - -v1 is the original version of the software, and is no longer supported. - -### v2 - -`mockery` is currently in v2, which originally included cosmetic and configuration improvements over v1, but also implements a number of quality-of-life additions. - -### v3 - -[v3](https://github.com/vektra/mockery/projects/3) will include a ground-up overhaul of the entire codebase and will completely change how mockery works internally and externally. The highlights of the project are: -- Moving towards a package-based model instead of a file-based model. `mockery` currently iterates over every file in a project and calls `package.Load` on each one, which is time-consuming. Moving towards a model where the entire package is loaded at once will dramatically reduce runtime, and will simplify logic. Additionally, supporting only a single mode of operation (package mode) will greatly increase the intuitiveness of the software. -- Configuration-driven generation. `v3` will be entirely driven by configuration, meaning: - * You specify the packages you want mocked, instead of relying on it auto-discovering your package. Auto-discovery in theory sounds great, but in practice it leads to a great amount of complexity for very little benefit. - * Package- or interface-specific overrides can be given that change mock generation settings on a granular level. This will allow your mocks to be generated in a heterogeneous manner, and will be made explicit by YAML configuration. - - Proper error reporting. Errors across the board will be done in accordance with modern Golang practices - - Variables in generated mocks will be given meaningful names. - - - Stargazers ----------