7 ms·
Hey I'm glad you asked! It's the way Nextjs handles urls with more than 1 param. If I prettify the URL then for some reason the page can't access them. Don't kn
by Octouroboros 6y ago
Hey I'm glad you asked! It's the way Nextjs handles urls with more than 1 param. If I prettify the URL then for some reason the page can't access them. Don't know if they've improved on it yet (or, who knows, maybe I'm just using it wrong) but it'll be fixed eventually.
- SamBam 6y agoThe URL parameters are: {"bookTitle": "The Call of Cthulhu", "displayTitle": "The Call of Cthulhu", "language": "English", "bookId": "5f468ca35e91c10be0883a57"} Why do you need all the others besides "bookId"? Changing "bookTitle" and "language" don't seem to do anything. Changing "displayTitle" does change the displayed title, but why can't you get that using the bookId?
- Minor49er 6y agoThat's interesting. Thanks for pointing me towards Next.js. I wasn't aware of that framework, but I'm checking it out.
- technoplato 6y agoSuper cool framework that is only getting better. If you’re interested in framework spelunking-check out Remix by Ryan Florence and Michael Jackson (no, not that one...). It’s actually going to be paid but I’m very excited to try it. It handles some data loading pain points among others that seem very interesting.
- roryokane 6y agoLink to the mentioned framework “Remix”: https://remix.run/ https://remix.run/
- cambalache 6y agoThat is just an email collecting form. Astroturfing?
- john_miller 6y ago// call /MyPage?par1=hello&par2=42 const MyPage = (props: { query: { par1: string; par2: number } }) => ( <div>{`${props.query.par1}-${props.query.par2}`}</div> );
- ffpip 6y agoI think only the bookID is necessary