codybarr / hearthstone-deck-builder Goto Github PK

• create cards table / model
• create seed / import card data
• create endpoints for cards (only need GETs for /cards and /cards/:card_id)

Estimate: 3 hours

• add logic to the card endpoint to take in a querystring q=searchTerm and return filtered results
• add logic to the deck endpoint to take in a querystring q=searchTerm and return filtered results

Estimate: 1h

• this is all client side so no api needs to be implemented, should be a pretty simple sort of modal / overlay and a shuffle function.
• make sure the example hand display is accessible

Estimate: 2h

• On the create new deck form there should be a button for importing a set of deck cards by using the deckstring (see the https://www.npmjs.com/package/deckstrings package).

Estimate: 1h

• have to add individual fields to search for to the GET /cards endpoint
  • Card Set
  • Class
  • Type (Minion, Spell, Weapon, etc.)
  • Cost

Estimate: 2h

• Need to add a button / text field for quickly copying a deckstring from the site to the actual hearthstone game client.
• May need to add some sort of middleware for converting a deck to a deckstring and adding a separate field for it before sending the response back to the client.

Again, see https://www.npmjs.com/package/deckstrings.

• create a new POST /decks endpoint
  • Should only permit a deck to be submitted that belongs to the currently logged in user.
• this will have to chain a POST to a new /deck-cards endpoint (that will add the cards belonging to the deck to the deck-cards table in the database).

Estimate: 2h

• create decks table / model
• create a table for cards referenced in decks (which will contain a deck_reference, card_reference, and quantity)
• create GET endpoints for decks (/decks and /decks/:deck_id)

Estimate: 2h

• create a PATCH endpoint for /decks/:deck_id that updates a provided deck.
  • will also have to make this first DELETE all existing entries belonging to this deck in /deck-cards then add new ones.

Estimate: 2h

• need to create a POST /users endpoint

Estimate: 2h

• create a PUT? endpoint at /decks/:deck_id/vote
  • payload will be either 1, 0, or -1 (1 upvotes, 0 removes vote, and -1 downvotes)

Note: I don't really know how this works out to the HTTP verb since you don't really know, or I don't think you should have to know what the current state of the DB is. The server should be able to respond accordingly.

Estimate: 1h

• add another GET endpoint to the /decks router for fetching decks belonging to the currently logged in user (maybe /decks/mine) - would pass in jwt in auth header then fetch a list of decks belonging to the decrypted user.

Note: Or maybe put the endpoint in the users service (eg. GET /users/:username/decks) (then we could also do like favorited cards etc. -> /users/:username/favorite-cards, etc.)

I think this second approach makes more sense. Then anybody would be able to visit /users/:username and view their decks, profile info, etc.

• create a DELETE endpoint for /decks/:deck_id
  • having a CASCADE rule in effect should auto delete corresponding entries in the deck-cards table.

Estimate: 1h