[go-nuts] Scope/Context in struct and interfaces design questions

Hi all! I need an gopher advice. What is more idiomatic and do you see any problems with my solutions? Problem: I have a repository(persistence layer) for TodoLists. TodoLists usually belongs to a user. My system also have super-user/admin interface which can access all TodoLists. I can imagin

[go-nuts] state of the art code organisation api services

Hi All! I'm new to go and mailing lists at all.. I need to build a REST-backend service for my app. first chi router looks good, isn't it? But more important, how to organise code? What are good practices/examples in golang world? Is it good idea to do it domain/module based? e.g. structs: