Rest API implementation for store

[Olamyy]

Hi @gbozee and @teenoh , Have we agreed on the model fields for users and store items discussed #11 (comment) ?

My branch currently has the following fields setup for a product.

• product_code
• unit_price
• image
• details

For the user models, I have

• username
• email
• as fields.

Can I go ahead with those?

[Olamyy]

To help with onboarding, I wrote a bunch of tests during the holiday in an attempt to make the project follow the TDD approach.
I'd push these tests as soon after work today.
@teenoh In the long run, the tests in two ways:

• Provide a general idea of the api implementation structure.
• Help with onboarding for new contributors.

[gbozee]

This works as a start.

[gbozee]

it would be nice to see the tests you came up with

[teenoh]

Looks great, I'll love to see the tests too

[Olamyy]

As mentioned, here's #17 the accompany pull request containing the tests.
Do review and let me know things I'd need to improve.

[gbozee]

I observed that you are making use of the default django fieldfield. This isn't exactly a problem but thinking about where we would host this which would be heroku for now and since they do not allow file access, we would want to make use of a third party image hosting provider like cloudinary. Its free for up to 1g or so. @Olamyy

[gbozee]

https://github.com/cloudinary/pycloudinary You can create an account but ensure that the config is passed as an environmental variable