Fix config bug where mockery crashes when package map is nil #730
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes a number of things related to config parsing.
packages
map contained a package that pointed to a nil value, mocker would crash because it expected the mapping to be non-empty. The PR changes it so that mockery gracefully handles cases like this by lazily injecting aconfig
map into the package.showconfig
, or really in any situation where you wanted to serialized the config using a yaml parser. The fix was to do a deep copy of the configuration whenever merging top-level with package-level config.Also moving to using gotestsum for test output. This provides a much cleaner overview of the tests that passed/failed.
Type of change
Version of Golang used when building/testing:
How Has This Been Tested?
Unit test
Checklist