emmaramirez / pokemon-nicknames Goto Github PK

Problem: pokemon images don't get updated with the filter, at least visually.

This is probably due to the fact that it takes in data via props, rather than state

• Add Pokemon formes + megas to database
• Make sure they work well in sorted view, (i.e. M-Charizard next to Charizard, not after Volcanion)
• Make sure they display and all images are available

AC

• Search component that returns array of Pokemon that start with specified string

AC

• Error Handling for
  • When fetch fails/API server goes offline
  • When user places nickname for invalid species
  • When an angular component fails to render

Proposal: restrict the possible text in the nickname field to just those which is allowed in Pokemon itself.

Ideally the homepage should look somewhat like what's in the mockup below, except of course, multiple Pokémon should fit on one page.

Standard:

And the mobile version:

Should check into the way the event is firing in order to fix this issue.

• Change database to deal with these values
• Change API to reflect this

AC

• Works on multiple viewpoints

The bulk of the work for this has been done, this issue is to record that.

AC:

• Uses Python/tornado on back-end
• Uses Angular on front-end
• Connects to our good old friend MongoDB

• Number of nicknames (Asc & Desc)
• Date created (Asc & Desc)
• Submitted by (Asc & Desc)

AC

• Overall design uses darker colors + main color (bright red)
• We ditch the vestiges of material design

If the user clicks the + X more nicknames button on a Pokemon, it should reveal the rest of that Pokemon's information (i.e. their extra nicknames).

Questions:

• Should there be a verification for votes?
• Should nicknames be sorted by votes?
• Should popular/unpopular nicknames have different styling?

AC:

• A vote component in each nickname

This is the issue for adding Gen 7 Pokes

• Add Gen 7 into database
• Test Gen 7 Additions