You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The responsive nivo Radar animates to the data in batches of 25 pokemons in view as you scroll through the Pokedex (rolodex). This works logically in development, with minor threshold adjustments in the observer, but is out of sync in production.
My hunch is that
Radar needs more fragmented side-effects to react to independently.
Do not rely on serverSideProps for the query data, although graphql-codegen-apollo-next-ssr was a game-changer in getting hooks to function on a pre-render outside of a function component.
Conversely, SSR is surely adding to the sync problem. CRA and/or divorcing the notion of pages from components could set the pokedex free
NextJS does not play well with ContextAPI as the tendency is to refresh the page between links unless NextLink wrapper is used, which is not easy to test in a hot-reload dev environment
On a side note, routing to pokemons/[name] is meant to capture that pokemon's segment of the radar. Only the route changes. Locally, this is relatively working as it freezes the radar svg's state at the moment of routing.
The text was updated successfully, but these errors were encountered:
The responsive nivo
Radar
animates to the data in batches of 25 pokemonsin view
as you scroll through thePokedex
(rolodex). This works logically in development, with minor threshold adjustments in the observer, but is out of sync in production.My hunch is that
Radar
needs more fragmented side-effects to react to independently.serverSideProps
for the query data, although graphql-codegen-apollo-next-ssr was a game-changer in getting hooks to function on a pre-render outside of a function component.CRA
and/or divorcing the notion ofpages
from components could set the pokedex freelinks
unlessNextLink
wrapper is used, which is not easy to test in a hot-reload dev environmentOn a side note, routing to
pokemons/[name]
is meant to capture that pokemon's segment of the radar. Only the route changes. Locally, this is relatively working as it freezes the radar svg's state at the moment of routing.The text was updated successfully, but these errors were encountered: