You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to use param4 (/:project) to link to the default project associated with a category (web dev or gamedev), I realized using the parameter in the link will always link to whatever the current param is, even though state sets things properly immediately after for displaying the project name and other elements of the param. What this means is I will HAVE to handle this navigation programattically (at least I believe). Working on handling the check and navigating properly if this is the case.
// Refactoring routes, and general way this 'web app' works. Making HomeView the default route, with a 'modal' over it which will be Landing Page. Instead of all this weird routing form Landing Page to Homeview, landing page will be an overlay that exists within HomeView, that is only present when the user is at /landing. Thinking of actually making the LandingPage an option for "HomeViewContent" that steels the entire viewport, so that HomeView is always there behind it.
0 commit comments