Lego Set Management Page

[stynan27]

User Story

As a BlockHeads user, I want a page to create, read, update, & delete Lego sets, so that I can manage my Lego sets

Acceptance Criteria

• [ ] Done when a webpage exists to display a Table of Lego sets.
• [ ] Done when the Welcome page routes to this new Set management page via the "Manage Sets" button.
• [ ] Done when this new set management page has the title "Manage Lego Sets".
• [ ] Done when this new page has a table to list managed Lego sets.
• [ ] Done when we have a backend application to service client Lego set to create, read, ~update~, & delete requests.
• [ ] Done when a client can create a new Lego set with fields for Set name, Number of parts, list of minifigure names, price, & PDF/image instructions.
• [ ] Done when a client can delete a set from the table of Lego sets.
• [ ] Done when a client can create a set in the table of Lego sets.
• [ ] Done when a client can update a set from the table of Lego sets.
• [ ] Done when a client can see their list of lego sets in the table ~- [ ] Done when a client can return to the manage sets page and view previously created/altered/edited list of sets after server shutdown (persistence layer).~ -> Will revisit with a future story to deploy the app to production.

[stynan27]

We decided that set updates are out of scope for this sprint. Will revisit in a future separate issue/story.

[stynan27]

Since there is a lot of functionality here would be a good idea to at least have some unit tests per controller endpoint and new react UI additions.

Unfortunately, our current Java setup is resulting in package errors when we attempt to unit test relating to the in-memory H2 database. We should make de-coupling the H2 Database a priority for next spring and then pull in a separate task to test.

TODO

• [ ] Unblock below testing by completing #35

~- [ ] Create unit tests for UI based on AC's above~ ~- [ ] Create unit tests for API based on AC's above~ ~- [ ] new subtask to track?~