gkats / dude-expenses-backend Goto Github PK

Create a Postgresql role and database to use for development.

Make sure the app can connect to the database upon initialization.

Add a migration for creating a table to hold expenses.

ID primary key auto incrementing
Price (in cents)
Date
Tag
Notes

It seems that somebody closes the stream handler. Maybe pass a copy to the logger?

Returns all expenses. Accepts a month parameter to filter expenses by date. If no month is given should return the current month.

How to setup config per environment (development and production)

• Database
• Logging
• JWT secret
• Server port

Probably in the request headers. Be able to decode the token and determine the user.

Accepts price, date, tag and notes.

Price must be decimal greater than zero. Date and tag cannot be blank.

If tag does not exist, create one. Notes are optional.

Responds with the validation errors if expense cannot be created.

Tags: can be multiple, need to do OR

• Create a users table (id (pk), email, password, created_at, updated_at)
• Create an index for email
• Add user_id foreign key in expenses table

• GET /expenses (query by user_id)
• POST /expenses (insert user_id too)

Accepts an email and a password. If the email and password combination matches that of an existing user, it should return a success response status.

Every framework has them 😄

We need to be able to do something like:

routes.Handle("/expenses", JsonResponse(CommonHeaders(Logging(Authentication(WithDBAccess(expenses.Index)))))

The API is a bit ugly, but the idea is that each middleware stack should access the response writer and the request and set up things for the next stack, until we reach our final handler in the chain, which could of course set things for an upper level middleware.

For example the logging middleware could gather some info before and after the request is handled, and log in the end (defer).

For authentication and authorization

Database, logging.

It should return an empty array

Create a script that goes through the db/ folder and executes all migrations in series.

Maybe it's worth it to check out existing packages for this.

POST /authentications. Should accept email and password params.

Check email and password combination and return an authentication token for the user.

Do we want to support authentication expiration?

Add created_at, updated_at timestamp columns. Should default to now().

Investigate possible solutions.

AWS, Heroku, AppEngine, ...

This issue is about creating a user account. The app should accept an email and a password.

Email should be unique. Password should be at least 6 characters.

On success, it should create a new user with the above information. On error, it should return the validation errors.

Encrypt user passwords in the database.

• Investigate logging solutions/practices for Go programs.
• Add a logger, configure it for production and development.
• Go through the app and check all places that need logging.

We only need seconds precision.

SET timezone = 'UTC'

Should be the first migration to run, ever.

Time period: From, to

Create a handler for authentication that acts as middleware.

Needs the app Env as input.