302 Username string // sql: `username`
303}
304
305// table DBPREFIXwordfilters306type Wordfilter struct {
307 ID int `json:"id"` // sql: `id`
308 BoardDirs *string `json:"boards"` // sql: `board_dirs`
296 IsDeleted bool // sql: `is_deleted`
297}
298
299// table: DBPREFIXusername_ban300type UsernameBan struct {
301 filenameOrUsernameBanBase
302 Username string // sql: `username`
283 IsActive bool `json:"-"` // sql: `is_active`
284}
285
286// table: DBPREFIXthreads287type Thread struct {
288 ID int // sql: `id`
289 BoardID int // sql: `board_id`
272 Data string // sql: `data`
273}
274
275// DBPREFIXstaff276type Staff struct {
277 ID int // sql: `id`
278 Username string // sql: `username`
264 Hidden bool // sql: `hidden`
265}
266
267// table: DBPREFIXsessions268type LoginSession struct {
269 ID int // sql: `id`
270 StaffID int // sql: `staff_id`
Doc comments work best as complete sentences, which allow a wide variety of automated presentations. The first sentence should be a one-sentence summary that starts with the name being declared.
If every doc comment begins with the name of the item it describes, you can use the doc subcommand of the go tool and run the output through grep.
See https://golang.org/doc/effective_go.html#commentary for more information on how to write good documentation.
package main
// This struct represents an cybernetically enhanced duck
type Duck struct {
}
package main
// Duck represents an cybernetically enhanced duck
type Duck struct {
}