attempting to do:
page_1 -> 2 pokeAPI consumptions:
1 for {name, url} ->
2 another API call loops over [bulbasaur, ivysaur, poke.name] and does pokeAPI call with every pokemon name to get img data
page_2 -> when clicking on page_1 data, it gets saved to the database
page 2 organizes pokemon by types. click on a pokemon on this page, and it brings to page_3
page 3 is the pokemon profile page which shows all the details about pokemon. greatly aided by dynamic routing in reactJS:
host:3000/pokemon/${pokename}
this feature would be benefitted by a data store that holds a single value (the pokemon of which the 3rd page is themed)
and wiped once the user navigates to another page that isn't the third page.
attempting to do: page_1 -> 2 pokeAPI consumptions: 1 for {name, url} -> 2 another API call loops over [bulbasaur, ivysaur, poke.name] and does pokeAPI call with every pokemon name to get img data
page_2 -> when clicking on page_1 data, it gets saved to the database page 2 organizes pokemon by types. click on a pokemon on this page, and it brings to page_3
page 3 is the pokemon profile page which shows all the details about pokemon. greatly aided by dynamic routing in reactJS: host:3000/pokemon/${pokename}
this feature would be benefitted by a data store that holds a single value (the pokemon of which the 3rd page is themed) and wiped once the user navigates to another page that isn't the third page.
error:
proposed approach:
possible improvements: