4 ms·
Routing is indeed another pain point especially with internationalisation and having multiple dynamic/translated paths to the same page. My issue with data fetc
by cersa8 4y ago
Routing is indeed another pain point especially with internationalisation and having multiple dynamic/translated paths to the same page. My issue with data fetching is about the depreciation of getInitialProps() without a good alternative in place: https://github.com/vercel/next.js/discussions/10874 https://github.com/vercel/next.js/discussions/10874
I need a single place to load site translations, user data and what not, preferably without refetching this data on each page transition.
I also briefly looked at Remix and love the routing, but do not necessarily want Remix to dictate how I mutate my data.
- steve_adams_86 4y agoYeah, we’re on the same page with getInitialProps. Next needs something which accomplishes what people want from that, but with ongoing support from the team. I think it’s a special circumstance but still important to support. I’m not aware of a work around at this point. How does remix dictate how you mutate your data?
- cersa8 4y ago"How does remix dictate how you mutate your data?" I didn't word it correctly as Remix doesn't dictate the model. It does seem to have a strong opinion on how to handle form submissions. Trying to closely follow the browsers native form api does make a lot of sense in most situations, but I like a more JavaScript heavy approach to form handling. Especially since I have a lot of complex form interactions.