feat: add support for a configuration file #32
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adamconnelly
force-pushed
the
adamc/kelpie-config
branch
from
7b4df52 to
d6f2d48
Compare
Added support for a kelpie.yaml file to specify the mocks to generate. The advantage of this is that we can avoid re-parsing the same package multiple times if we're generating more than one mock from it. The existing `go:generate` method of generation is still supported - this will be up to personal preference. I've also added some extra output to the generate command to make it easier to tell if the mocks have been generated correctly or not.
adamconnelly
force-pushed
the
adamc/kelpie-config
branch
from
d6f2d48 to
c1bacd3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added support for a kelpie.yaml file to specify the mocks to generate. The advantage of this is that we can avoid re-parsing the same package multiple times if we're generating more than one mock from it.
The existing
go:generatemethod of generation is still supported - this will be up to personal preference.I've also added some extra output to the generate command to make it easier to tell if the mocks have been generated correctly or not.
TODO: