wdi-10-chi

Title: Pokedex
Type: Lab
Duration: several hours
Creator: Thom Page WDIr-Panthalassa
Adapted by: Kristyn Bryan
And then by: Reuben Ayres for wdi-10-chi fluff-hounds

Full CRUD and REST with Express:

App: Make a POKEDEX

Your mission is to make a Pokémon character manager (a Pokédex).

All you are given is a pokemon.js file that has all the raw data for 151 Pokémon (it's over 50,000 lines of code). You can render this as JSON in your browser. If you decide to check it out in your text editor, don't click on or open this file unless you are prepared to wait a minute or so for it to load. It is a huge file.

It is up to you how you build your app, in what order you want to do things, what kind of design flow your app will have, where you put your delete button, etc, and what parts of the Pokémon data your pages will display.

There are a few requirements to keep in mind:

MVP

The app will:

display a bunch of Pokémon images on the index
have separate show pages for each Pokémon
have the ability to add a new Pokémon
have the ability to edit existing Pokémon
have the ability to delete Pokémon

Setup

Your app should follow the MVC format of models, views, and controllers.

You will want a folder each for Models, Views, and Controllers.

Routes

The app will use all seven RESTful Routes from our list:

Index
- GET /pokemon

- Show - GET `/pokemon/:id`
- New - GET `/pokemon/new`
- Edit - GET `/pokemon/:id/edit`
- Create - POST `/pokemon`
- Update - PUT `/pokemon/:id`
- Destroy - DELETE `/pokemon/:id`

Starter Code

// server.js

const express    = require('express'),
    app        = express(),
    Pokemon    = require('../models/pokemon.js');

// INDEX
app.get('/', (req, res) => {
	res.render('index.ejs', { data: Pokemon });
});

// SHOW
app.get('/:id', (req, res) => {
    res.render('show.ejs', { data: Pokemon[req.params.id] });
});

Data

Notes on the Pokémon data and what to display

The pokemon.js file is massive and there is a ton of data to parse through. You need not display all of it on your pages. On your index page, you can just render the images, and maybe the pokemon's name.

Here are suggestions for what to display on your Pokémon's show page:

The pokemon's name
The image of the pokemon
An unordered list of the Pokemon's types (eg. water, poison, etc).
The pokemon's stats for HP, ATTACK, and DEFENSE.

Notes on testing

Sometimes you don't want to have to build out a view or a form in order to test if a POST, PUT, or DELETE route is working. Use Postman on these routes and console.log a message and/or req.body to see if the route is working, and worry about the view later.

Commits

The exact order of your commits is up to you, but refer back to the MVP to make sure that you're meeting all of the requirements. Make your commits after get one new piece of the work completed and functioning. Commits should be terse and clear and describe functionality added in non-code language (answers the question "what does the app DO now that it couldn't before").

Examples (not an exhaustive list):

"Server is working and displays a plain index page"
"Displays a bunch of Pokémon images on the index".
"Separate show pages for each Pokémon".
"Created and an add pokemon page" (e.g. after you successfully create and rendered a template like new.ejs)
"User can add a new Pokémon". (e.g. when your 'add pokemon' page successfully POSTs to your app.post('/pokemon') route)
"Has an 'edit pokemon' page". (e.g. edit.ejs rendered)
"Ability to edit existing Pokémon". (e.g. app.put works)
"Has the ability to delete Pokémon".
"The app uses RESTful routing, all seven RESTful routes".
"The app uses the MVC pattern established with views and models".

Once you have all seven restful routes working...

Style your App!

Use static assets
Make your app look and act nicely with static assets (set up a public folder and add some css, js)-- try using jQuery.

Commits might include:

"Static assets included - basic CSS and jQuery".
"Set up Gulp for compiling LESS"
"Styled app with less"

Need some style inspiration?

These are screenshots from what other students have done to their Pokedex:

All styled up

Investigation

If you get everything done, make a copy of this pokedex lab app you just built. Look into using the mongodb node package with express within your copy: https://www.npmjs.com/package/mongodb

Try to connect your app to a mongo db. Investigate how you can do Read operations, and then how to do Create operations inside the controller in your app. You might want to seed your Mongo db with select Pokémon data.

Note that this is advanced, and is not how we will be doing Mongo queries inside our app in the future. Instead, we will be using a node package called Mongoose which uses different commands.

Nevertheless, it is worth your time to investigate how to get mongo connected to your app, and how to make raw mongo queries within it, even if you get absolutely nowhere with it.

webermn15/wdi-10-lab-and-hw-12-Pokedex-Full-CRUD