Thank you so much for the article, Alexey! Quick question: can you explain more on the part where the code renders special_string and special_int based on the intValue? Why did we parse the intValue from the :special_value query?
I added that as a random example of some custom logic that operates on routes - which is one advantage of using express together with NextJS. There's no special significance to parsing the int itself.
But thanks for pointing out the issue. I'll try to improve the article and code so hopefully the examples are more realistic.
Thank you so much for the article, Alexey! Quick question: can you explain more on the part where the code renders special_string and special_int based on the intValue? Why did we parse the intValue from the :special_value query?
Hey Peter! Glad you liked the article :)
I added that as a random example of some custom logic that operates on routes - which is one advantage of using express together with NextJS. There's no special significance to parsing the int itself.
But thanks for pointing out the issue. I'll try to improve the article and code so hopefully the examples are more realistic.
I updated the repository - hopefully the new examples make a bit more sense. Also updated the article to explain the examples better.