pegomock

What's Changed

• rename mockgen variables like _ret1, _result and _params not to conflict with method args by @krrrr38 in https://github.com/petergtz/pegomock/pull/124
• Explicitly validate the len of params to ensure we don't get index ou… by @AndrewRPorter in https://github.com/petergtz/pegomock/pull/126

New Contributors

• @krrrr38 made their first contribution in https://github.com/petergtz/pegomock/pull/124
• @AndrewRPorter made their first contribution in https://github.com/petergtz/pegomock/pull/126

Full Changelog: https://github.com/petergtz/pegomock/compare/v4.0.0...v4.1.0

Changes

This release removes a lot of cruft from Pegomock. Reflection-based and sourced-based mock generation have been removed, because they don't support generics. The only and default method for mock generation is based on golang.org/x/tools/go/packages.

It also removes a lot matchers and matcher code, that is not necessary anymore, now that matchers can use generics too.

The README was updated to document these changes.

Migrating code from v3 to v4

Replace all matcher calls such as EqString(...) and EqInt(...) with the simpler Eq(...).

Changes

• Fix bug where generated files would have a wrong import name for the pegomock package

This release drops support for non-Go modules based setups. For those still requiring this support, it's recommended to stick with version 2.

There are no breaking API changes with the switch to v3. Migration from version 1 or 2 involves two steps:

1. Change import paths as follows:

   -import "github.com/petergtz/pegomock"
   +import "github.com/petergtz/pegomock/v3"
   

2. Install the latest pegomock binary via

   go install github.com/petergtz/pegomock/v3/pegomock@latest
   

For step 1, make sure to change sub-packages as follows:

-import "github.com/petergtz/pegomock/ginkgo_compatible"
+import "github.com/petergtz/pegomock/v3/ginkgo_compatible"

Changes

• Fix empty unnamed struct matcher generation (https://github.com/petergtz/pegomock/pull/109)
• Add NotEqualsMatcher and generated matcher factory (https://github.com/petergtz/pegomock/pull/113)
• Extracting separate ArgumentMatcher ifc with no FailureMessage (https://github.com/petergtz/pegomock/pull/114)

Changes

• Fix "Too many open files" error in remove command (https://github.com/petergtz/pegomock/pull/99)
• Fix a bug when multiple interfaces were parsed (https://github.com/petergtz/pegomock/pull/104)
• Add issue template
• Avoid duplicate imports when generating matchers of map types (https://github.com/petergtz/pegomock/pull/106)

Sorry, this is basically a release with no changes, but I realized I had published 2.6.0 without having its commits on master and that seemed weird. However, I couldn't just fast-forward master, because it had already diverged. Hence, publishing this pseudo-release. Now everything should be in sync again. Yay!

Changes

• Fix logic when empty variadic arg is provided (https://github.com/petergtz/pegomock/issues/87)
• Generate custom matchers for variadic types (https://github.com/petergtz/pegomock/issues/90)
• Add missing matcher and InOrderContext to ginkgo_compatible (https://github.com/petergtz/pegomock/issues/80)
• Commit generated matchers for pegomock tests (https://github.com/petergtz/pegomock/issues/91)

Changes

• Add support for recursively embedded interfaces.

Changes

• Add support for Go modules, i.e. pegomock can generate mocks in a directory outside of GOPATH (thanks, @MrCreosote)

Changes

• Allow channels with no direction as return value for callback stubs, even when return type has a direction.

Changes

• Make sure numbered import paths have a stable sort order between generate commands to avoid unnecessary diffs. Thanks @hferentschik for the PR.

Changes

• Introduce new CLI flag --mock-name to customize the generated mock name (Thanks @relnod)
• Fix channel directions in generated mocks when using flag --use-experimental-model-gen (Thanks @lkysow)
• Use stable Go version in Travis CI build instead of tip

Changes

Undo package name determination through AST parsing

This is not covering certain use cases and needs more testing before it can be made available.

See also: https://github.com/petergtz/pegomock/issues/77

Changes

This release fixes the package name generation by using a smarter algorithm. Specifically directories with dashes in the directory base names have bitten people more than once in the past (including me).

Here's how the new algorithm works: It first checks if there are already _test.go files in the directory where the mock file is created and uses the test package name if possible. If no test files are present it looks for .go files and uses their package name + _test. If no .go files exist at all in the directory, it uses the directory base name and converts potential -s to _s to make Go happy.

This algorithm is a bit slower than code used to be, but also more robust. If people see a problem with that, please open an issue. A workaround is to simply provide the package name via --package. That will be very fast.

Changes

• Use goreleaser from now on to provide binaries along with releases

Changes

This major release introduces non-global fail handlers. Check the documentation on how to set up the mocks. Also, please re-generate your mock files to make it compatible with this version of Pegomock.

Pegomock has been in use by several people and organizations, and has stabilized over the time. It seems to be the right time to mark the current version as 1.0.0.

Versioning will also make it possible to introduce changes that will require re-generating existing mocks and communicate such changes to users by bumping the major version number.