Specification

Create, build and connect a MySQL database through JDBC.

To Do

Create an ER-Diagram for the database to have a plan for what tables and columns we will use
and after that build the database and connect it.

Done

First sketch of the ER-Diagram is done, we can start building the MySQL Database.

The repo is looking awfully empty right now. It would probably be a good idea to add the framework to work off.

What to do

Commit the base spring framework, with all the specified dependencies, to main.

When it is done

It's done when main has, and in turn dev, has the baseline we're looking to work with.

Specification

The user can't add items to their shopping carts due to lack of functionality. Soon enough they'll get real mad.

To Do

Create a service controller called ShoppingServiceController. In this controller add methods that relates to shopping, such as adding items to cart, summarizing cost, removing items from carts, and creating a new delivery row with needed data.

Done

This issue is considered clear when the specified methods are implemented and tested with dummy data.

Specification

The base of the application is starting to look solid, , least in a basic sense of spring. We should start spending some time looking trough Twitter's API.

To Do

Study the twitter API through their documentation and by using the postman services.

Done

This issue is conisdered done when the person assigned has a rudimentary understanding of the API and can make calls with it trough postman and a test application.

Specification

Right now there is an error on startup that is tied to the spring boot started data jpa. It's in part related to the choice of database.

To Do

The group decides what form of database we should build the application around and the program attached to it. Some examples being Postgress, MSQL Server, MongoDB, and Derby.

Done

This issue is considered done when a database type has been decided and implemented, no error should occur on startup.

Specification

Create a baseline api for the webshop, the basis of it all is the products so make the CRUD routes for that. The api should be following REST standards.

This issue is now tied to #7

To Do

Write Create, Read, Update, and Delete routes for a product controller. Exception handling is to be expected. Use this as an chance to learn spring mapping.

Done

This issue should be considered done when products has its four basic routes as well as excpetions for them and relevant options.

Specification

The models and entities have been set up with basic CRUD features. Now we should try and make them connected to one another so we can create advanced custom queries.

To Do

Assign relations between all the tables inside spring. Read Thor's presentations regarding it to create a functional example.

Done

This is considered done when all entities have been set up with the correct value pairs/foreign keys.

Specification

Create a more routes for the webshop, we can use #5 as a base for further development of the otehr routes.

To Do

Write Create, Read, Update, and Delete routes for a Employees, Manufacturers, and Shipment controller. Exception handling is to be expected. Use this as an chance to learn spring mapping.

Done

This issue should be considered done when the three controllers has their four basic routes as well as excpetions for them and relevant options.