React and Graphql
Hi,
What is your opinion about, use React and Graphql for the client side?

I looked at the code. there is
- a problem with id (int64) (no support in js)
- user data move to redis

uid https://blog.kowalczyk.info/article/JyRZ/generating-good-unique-ids-in-go.html
It's cool that you're interested in this, would you submit a PR?
Standard Go Project Layout
https://github.com/golang-standards/project-layout
https://github.com/alexsuslov/gobb/tree/change_int_id_to_string
DONE
- add graphql
- add hello world
- graphql type generator
DO
- change int64 ID to string
TODO
- [query] get post by id
- [query] get board by id
What do you think about using int (i.e. int32) instead of a UUID? A UUID seems like overkill for most Gobb usecases. It would still solve your js support issue I think? Just a thought. Really nice work on this!
int32 it's more easy
int64 -> int
Need:
- type NullInt struct{}
- template "admin_topbar"

https://github.com/alexsuslov/gobb/blob/change_int64_id_to_int/TODO.md
What do u think about:
type Post struct {
ID int `db:"id"`
Message string `db:"title"` // 140 char
OwnerID int `db:"owner_id"`
CreatedOn time.Time `db:"created_on"`
UpdatedOn time.Time `db:"updated_on"`
}
type PostDescription struct {
PostId int `db:"post_id"`
Description string `db:"description"`
}
// https://www.postgresql.org/docs/current/datatype-geometric.html#idm46428712347808
type PostGeo struct {
PostId int `db:"id"`
Point point `db:"point"`
}
type PostTag struct {
PostId int `db:"post_id"`
TagId int `db:"tag_Id"`
}
type PostSocial struct {
PostId int `db:"post_id"`
Starts int `db:"stars"` //0-5
Like bool `db:"like"`
}
type PostFollow struct {
PostId int `db:"post_id"`
followId int `db:"follow_id"`
}