-
Notifications
You must be signed in to change notification settings - Fork 570
feat(type): generate type with no crud operation #990
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
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.
Good addition for advanced users 👍
integration/cmd_type_test.go
Outdated
|
|
||
| env.Must(env.Exec("should prevent creating a legacy type with no message", | ||
| step.NewSteps(step.New( | ||
| step.Exec("starport", "type", "nomessagelegacy", "--no-message", "--legacy"), |
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.
Do we need to support -legacy at all?
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.
Because we still have --legacy option, I can remove this test now that we know we'll stop supporting this
Part of #967
The flag
--no-messageallows to generate a type without interaction message.Queries are still generated.
To test:
In
msg_server_makefo.go:For templates the pattern is:
That can be discussed, this pattern would be used for other component like indexed type or packet