Here's the relevant paragraph from the guide you linked to (emphasis mine):
Note how goagen generated a main.go for our app as well as a skeleton > controller (bottle.go). These two files are meant to help bootstrap a new > development, *they won’t be re-generated (by default) if already present* > (re-run the tool again and note how it only generates the files under the > app, client, tool and swagger directories this time). This behavior and > many other aspects are configurable via command line arguments, see the > goagen docs for details. > On Saturday, December 24, 2016 at 4:34:14 PM UTC+1, Tong Sun wrote: > > Wow, quite impressive. I wish I had known it earlier. > > One quick question, how does goa support round-robin design? I.e., from > https://goa.design/learn/guide/ that I quickly peeked, it says > > - use goa to generate a complete implementation, including bottle.go > - Then manually edit the bottle.go file > > So what would happen if I have edited the bottle.go file, but want to > tweak my design afterward? > > Thanks > > On Tuesday, December 20, 2016 at 7:39:17 PM UTC-5, br...@gophertrain.com > wrote: >> >> take a look at goa and gorma: https://goa.design >> >> goa generates an API from your description DSL, and Gorma generates the >> data access layer. It uses gorm under the scenes so you'll have an easy >> route to migration. >> >> Brian >> >> On Tuesday, December 20, 2016 at 8:46:12 AM UTC-5, Thomas Bellembois >> wrote: >>> >>> Hello, >>> >>> I have an application that define structures >>> >>> type Team struct { >>> ID uint `gorm:"primary_key"` >>> Name string `json:"Name"` >>> } >>> type MailingList struct { >>> ID uint `gorm:"primary_key"` >>> Name string `json:"Name"` >>> Comment string `json:"Comment"` >>> } >>> ... >>> >>> and handlers to manage CRUD operations >>> >>> func TeamUpdateHandler(w http.ResponseWriter, r *http.Request) >>> func TeamCreateHandler(w http.ResponseWriter, r *http.Request) >>> func TeamDeleteHandler(w http.ResponseWriter, r *http.Request) >>> func TeamReadHandler(w http.ResponseWriter, r *http.Request) >>> func MailingListUpdateHandler(w http.ResponseWriter, r *http.Request) >>> func MailingListCreateHandler(w http.ResponseWriter, r *http.Request) >>> func MailingListDeleteHandler(w http.ResponseWriter, r *http.Request) >>> func MailingListReadHandler(w http.ResponseWriter, r *http.Request) >>> >>> Is there a way in Go to define a CRUD-like model with only 4 generic >>> handlers to manage this operations ? >>> >>> Regards, >>> >>> Thomas >>> >>> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
