Refactor/organize context #59
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Description
This pull request refactors the authentication and Piazza context management in the frontend React app. It introduces new context providers for user authentication and Piazza tab information, and updates all related components to use these contexts for state and actions. This change centralizes logic, improves code organization, and removes redundant state handling from individual components.
Context Provider Introduction and Integration
UserAuthProviderandPiazzaProvidercontext components infrontend/src/context/UserAuthContext.jsxandfrontend/src/context/PiazzaContext.jsx, encapsulating authentication and Piazza tab logic for use throughout the app.frontend/src/popup/main.jsxto ensure global access to authentication and Piazza state.Component Refactoring to Use Context
App,DashboardPage,AssistantPage, andLoginPagecomponents to consume authentication and Piazza state/actions from context, removing local state and redundant prop drilling.Code Simplification and Cleanup
These changes streamline state management, improve code readability, and make it easier to extend authentication and Piazza-related functionality in the future.
🎯 Type of Change
🧪 Testing
📋 Checklist
📸 Screenshots (if applicable)
N/A
🔗 Related Issues
This might be useful for #45