Open Arafatmollik1 opened 4 months ago
Fundy application will not have any home page. Rather, a route called tickets/[eventID] An event id decides what is the event about.
The route tickets/[eventID] will have the following properties.
The login button will send user to login page
The buy ticket button will console.log buy ticket button clicked.
So do the following steps.
Make the tickets/[eventID]
Make the mockUI Make a mock UI with static Data. In a future issue we can make dynamic data fetching.
Modify login functionalities so that, after login every reload will check if the user is logged in or not. One strategy can be that when the user logs in a session will be created "userLoggedIn = true" and we can validate based on that. The session shall have a timeout. here are some nice documentation- https://nextjs.org/docs/app/building-your-application/authentication https://clerk.com/blog/complete-guide-session-management-nextjs https://nextjsstarter.com/blog/nextjs-13-server-side-session-management-guide/
@AR-Aourangazeb-Alif You can get started with this. :) NOTE-> Pull develop branch first
Fundy application will not have any home page. Rather, a route called tickets/[eventID] An event id decides what is the event about.
The route tickets/[eventID] will have the following properties.
The login button will send user to login page
The buy ticket button will console.log buy ticket button clicked.
So do the following steps.
Make the tickets/[eventID]
Make the mockUI Make a mock UI with static Data. In a future issue we can make dynamic data fetching.
Modify login functionalities so that, after login every reload will check if the user is logged in or not. One strategy can be that when the user logs in a session will be created "userLoggedIn = true" and we can validate based on that. The session shall have a timeout. here are some nice documentation- https://nextjs.org/docs/app/building-your-application/authentication https://clerk.com/blog/complete-guide-session-management-nextjs https://nextjsstarter.com/blog/nextjs-13-server-side-session-management-guide/