At the moment we are using/setting a react state on the client to dynamically display content. Once the form has been filled we show the degree planner. However, I don't think this is the right way of doing such a thing.
I think we should introduce some globalised state management.
Check if degree details are available (either from setting global state of from login data in the future)
If the global state has not been set we redirect from /degreePlanner to a separate degreeDetailsForm links with #7.
[ ] This issue will simply be creating a new route with the Next.Js for the form and removing detailsForm and the local state management the form from /degreePlanner
At the moment we are using/setting a react state on the client to dynamically display content. Once the form has been filled we show the degree planner. However, I don't think this is the right way of doing such a thing.
I think we should introduce some globalised state management.
Check if degree details are available (either from setting global state of from login data in the future)
If the global state has not been set we redirect from
/degreePlanner
to a separatedegreeDetailsForm
links with #7.Using https://nextjs.org/docs/app/building-your-application/routing/redirecting
[ ] This issue will simply be creating a new route with the Next.Js for the form and removing
detailsForm
and the local state management the form from/degreePlanner
[ ] localStorage validation timestamp = 2 days