-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add kitgen README #743
Add kitgen README #743
Conversation
- add installation and running instructions - add disclaimer - add introdctory note on experimental nature of the project
- github markdown apparently fails to keep track of `1. - 1. - 1.` style list if block code is involved - thought it was the double space at the end of the code block, but removing didn't help
👇🏻haven't touched those failing tests. |
PostProfile(ctx context.Context, p Profile) error | ||
// ... | ||
} | ||
type Profile struct { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nyarly I went off your profilesvc example in writing this, and now I realize that kitgen doesn't work on an input containing type definitions (and single interface). Not sure what's up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems reasonable to me but I'll wait for a plus-one from @nyarly |
@peterbourgon perhaps add him as a reviewer? |
LGTM. Sorry about the delay here. I didn't remember that there was a dependency on inlinefiles. Should look at that and see if it can be migrated to the more conventional go:generate pattern. |
@nyarly if you want a tester — I am running kitgen almost daily atm. |
Thanks! |
This measly PR with absolutely no code change and no performance improvements seeks to address #639 with a bit of note-taking.
/request @nyarly