fossapps / golang_starter Goto Github PK

should describe directory structure,
how one can continue working on this
etc, note on command line tools

like redis can go to redis package

When a event occurs, dispatch an action, depending on what event is, one could perform side effects, like sending activation email when user signs up, or performing real delete from everywhere else when user is deleted, etc

• adapters/must_have_permission should use request helper instead
• remove the helper/registration
• integration test for redis?
• naming convention for mock files and interface
• user.update should actually check if there's password and crypt it

need to add more error handling like in config

• ensure valid config during application startup
• db/devices.go
• db/migrations.go
• db/permissions.go
• db/refresh_tokens
• db/users.go
• migrations/migration_manager.go (after db/migrations)
• migrations/permissions_seed.go

during last refactor, jwt was moved to separate package, now it's time it's tested.

organize into 3 categories:
standard library, our own imports, 3rd party dependencies

(look for more examples)

redis/ratelimiter and rate limiter can be in different package (redis can be different package)