fix 404 on dynamic routes [profile page]

[nagarajpandith]

• on opening any user's profile page, a 404 error and loading icon appears together. if user exists-> both 404 and loader disappear and profile page renders as expected. if user doesn't exist, 404 stays, loader disappears.
• this is because next.js does not know if the path exists or not. hence returns a 404 first and then renders the page.
• fix this by using getStaticPaths to tell Next.js which and all usernames are available and must be made a valid route and getServerSideProps to fetch user data and return profile data back to main function component

[NidheeshaT]

fix this by using getStaticPaths to tell Next.js which and all usernames are available and must be made a valid route and getServerSideProps to fetch user data and return profile data back to main function component

I think that's not why it is showing 404 page, its because of

The loading is already checked here https://github.com/FiniteLoop-NMAMIT/flc-website/blob/c5a62a01d994b7e4069049ccf59af60f52ad4da5/src/components/profile/index.tsx#L237-L240

But you after that you check if data is not there then display 404 page but this happens when loading as data is still yet to come https://github.com/FiniteLoop-NMAMIT/flc-website/blob/c5a62a01d994b7e4069049ccf59af60f52ad4da5/src/components/profile/index.tsx#L263

Please correct me if I'm wrong🤲

[nagarajpandith]

oh, i didn't observe the component being used manually. i assumed it was next.js which was throwing 404. thank you for pointing out🙏🏼 fixed it in 33c2c1c64b1823ac398f2723431b5d5006cebb96