Problem Statement
Profile action buttons currently use hash-based navigation. The app itself uses page state navigation, so behavior is inconsistent and harder to maintain.
Proposed Approach
Add a page navigation callback in App and pass it to UserProfile.
Replace hash-based button handlers with callback-based page switching.
Make Create Your First Event open create-event page.
Make Browse Events open event-list page.
Remove any active hash navigation usage related to these buttons.
Verify navigation works in authenticated flow.
Files and Scope
event-dappp/src/App.js
event-dappp/src/components/UserProfile.jsx
Acceptance Criteria
Test Plan
Open profile page after login.
Click Create Your First Event and confirm create-event page opens.
Click Browse Events and confirm event-list page opens.
Confirm URL hash is not used for these actions.
Risks and Edge Cases
Possible regression in page switching if callback is not passed correctly.
Must ensure behavior still works when user is not authenticated.
Problem Statement
Profile action buttons currently use hash-based navigation. The app itself uses page state navigation, so behavior is inconsistent and harder to maintain.
Proposed Approach
Add a page navigation callback in App and pass it to UserProfile.
Replace hash-based button handlers with callback-based page switching.
Make Create Your First Event open create-event page.
Make Browse Events open event-list page.
Remove any active hash navigation usage related to these buttons.
Verify navigation works in authenticated flow.
Files and Scope
event-dappp/src/App.js
event-dappp/src/components/UserProfile.jsx
Acceptance Criteria
Test Plan
Open profile page after login.
Click Create Your First Event and confirm create-event page opens.
Click Browse Events and confirm event-list page opens.
Confirm URL hash is not used for these actions.
Risks and Edge Cases
Possible regression in page switching if callback is not passed correctly.
Must ensure behavior still works when user is not authenticated.