-
Notifications
You must be signed in to change notification settings - Fork 563
feat: scaffold empty message #823
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
Conversation
Really like this functionality! 🔥 I would probably make description optional with a flag Also, aren't we better off creating new files, instead of doing string replacement? I'm thinking about scaffolding |
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.
👏
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.
Nice work! 🍷
@ltacker can we rm *-packr.go
files? Btw, I'm really curious how they are generated even, because we removed packr
boxes and switched to embed
. Are you using an older version of our Makefile
by any chance?
I don't know maybe a merging issue |
* Templates * Scaffolder * Add command * Tests for message * Fix some bugs * Makes description optional * Format * Fix response field * Remove pack
starport message foo "Create a foo" bar foobar:int barfoo:bool --res foo,bar
Will generates:
in
msg_server_foo.go