Content
@
0 reply
0 recast
0 reaction
ksaitor
@ksaitor
trying out App Router for the first time on a new project terrified. wondering how long will it take for me before i decide to revert back to Pages?
1 reply
0 recast
0 reaction
Haardik
@haardikkk
It’ll be fine, async components start feeling really nice after you get used to separating components into files a bit more often than pages router
1 reply
0 recast
1 reaction
ksaitor
@ksaitor
Current challenge: I have a complex form, where most of it is implemented through server side actions, but some fields need real time client side interactions. So it's a vital confusion that I need to implement a tiny part of the form in a separate file, just to make it "use client". With page router it would have been just one component in one file... What are some best practices here?
1 reply
0 recast
1 reaction
Haardik
@haardikkk
Yeah… break it up
1 reply
0 recast
0 reaction
ksaitor
@ksaitor
Very weird experience. Wasn't sure I was doing this right... but let's see over time, if this end up being technical debt or not.
1 reply
0 recast
1 reaction
Haardik
@haardikkk
What’s the component that needs interaction? There may be a diff way of doing this
1 reply
0 recast
0 reaction
ksaitor
@ksaitor
For example job submission form on https://cryptojobslist.com/hire-blockchain-talent Currently it's on Pages router. If I were to move it to App router, I need a bunch of fields to be validated on the fly, form fields need to change based on previous user input (eg Application Method). In my new app the form is much simpler, but the problem remains the same - need to dynamically react to user input before the form is submitted.
1 reply
0 recast
0 reaction
Haardik
@haardikkk
yeah this is an unfortunate case for the app router just make the whole thing a client side component if its too much of a hassle to be honest, its fine
1 reply
0 recast
0 reaction
