Skip to content

Commit ba0fbe9

Browse files
authored
Update README.md
1 parent 5a3e47a commit ba0fbe9

File tree

1 file changed

+0
-23
lines changed

1 file changed

+0
-23
lines changed

README.md

-23
Original file line numberDiff line numberDiff line change
@@ -26,29 +26,6 @@ $ task test
2626
task: [test] go test -v -coverprofile=coverage.txt ./...
2727
```
2828

29-
Development Efforts
30-
-------------------
31-
32-
### v1
33-
34-
v1 is the original version of the software, and is no longer supported.
35-
36-
### v2
37-
38-
`mockery` is currently in v2, which originally included cosmetic and configuration improvements over v1, but also implements a number of quality-of-life additions.
39-
40-
### v3
41-
42-
[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:
43-
- 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.
44-
- Configuration-driven generation. `v3` will be entirely driven by configuration, meaning:
45-
* 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.
46-
* 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.
47-
- Proper error reporting. Errors across the board will be done in accordance with modern Golang practices
48-
- Variables in generated mocks will be given meaningful names.
49-
50-
51-
5229
Stargazers
5330
----------
5431

0 commit comments

Comments
 (0)