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
As a user, I would like each Vinmonopol to have a unique URL within Winmonopolet in order to …
… bookmark the Vinmonopol and access it more quickly
… send a URL to someone to help them navigate the page more quickly
… reload the page if some technical error occurred
I also subconsciously appreciate pages that load more quickly, so if page renders and navigation became quicker as a side effect of unique URLs, I would not complain.
Suggested solution
Use some kind of routing package, like react-router or nextjs to handle page routing. Of these two, the issue reporter thinks that nextjs would be the better pick. As hinted at in the problem description, users (and web search crawlers) like pre-fetched links and server-side rendered pages, so the chosen routing solution should enable this.
Future improvements that affect current implementation
A possible future improvement for the page could be storing the display filters (preferred beer types, price range) as query parameters of the URL. To keep the number of changed lines small in this first commit, "filters as query parameters" should probably be left to a later PR, but the possibility of extending the application this way should be kept in mind when choosing the routing package.
The text was updated successfully, but these errors were encountered:
As a user, I would like each Vinmonopol to have a unique URL within Winmonopolet in order to …
I also subconsciously appreciate pages that load more quickly, so if page renders and navigation became quicker as a side effect of unique URLs, I would not complain.
Suggested solution
Use some kind of routing package, like
react-router
ornextjs
to handle page routing. Of these two, the issue reporter thinks that nextjs would be the better pick. As hinted at in the problem description, users (and web search crawlers) like pre-fetched links and server-side rendered pages, so the chosen routing solution should enable this.Future improvements that affect current implementation
A possible future improvement for the page could be storing the display filters (preferred beer types, price range) as query parameters of the URL. To keep the number of changed lines small in this first commit, "filters as query parameters" should probably be left to a later PR, but the possibility of extending the application this way should be kept in mind when choosing the routing package.
The text was updated successfully, but these errors were encountered: