Feature: Project Lifecycle Management Detail Page#79
Open
vivek0369 wants to merge 5 commits intoNexGenStudioDev:masterfrom
Open
Feature: Project Lifecycle Management Detail Page#79vivek0369 wants to merge 5 commits intoNexGenStudioDev:masterfrom
vivek0369 wants to merge 5 commits intoNexGenStudioDev:masterfrom
Conversation
Contributor
There was a problem hiding this comment.
Code Review
This pull request introduces a comprehensive Task Management system and a detailed Project View feature, including RBAC via a PermissionProvider, new routing, and various UI components. Feedback focused on performance optimizations, such as memoizing sorted lists and reducing redundant array filtering. Additionally, logic improvements were suggested for the scoring system, and UI consistency was addressed by recommending custom modals instead of native browser alerts.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Member
|
@vivek0369 please check the master branch one please sync the project so that you got the latest code once you got the latest code merge it with your branch and push your changes again |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
Implement a fully functional, role-aware Project Detail Page that serves as the central execution and evaluation layer for projects. The page should support the complete project lifecycle including viewing, submission, judging, moderation, and activity tracking with a modern glassmorphism dark-mode UI.
✨ Features to Implement
1. Routing Setup
Add a protected route:
under the
/orglayout inApp.tsx.Example:
2. Mock API Service
Create:
The service should simulate backend APIs with artificial delays and mock data storage.
Required APIs
getProject(projectId)submitProject(projectId)Draft→Submitted.scoreProject(projectId, scoreData)moderateProject(projectId, action)deleteProject(projectId)🎭 Role-Based UI Behavior
👨💻 Participant View
Draftstate.⚖️ Judge View
Display a dedicated Judge Scoring Panel:
🛡️ Organizer/Admin View
Display Moderation Panel:
📌 Core UI Sections
🔹 Header Panel
Dynamic project status badges:
🔹 Project Overview
🔹 Team Section
🔹 Activity Timeline
Vertical timeline showing:
🎨 UI/UX Requirements
✅ Validation & Edge Cases
projectIdhandling🧪 Testing Instructions
Run:
Visit:
Use the temporary role switcher to test:
Verify:
📂 Suggested Structure
🏷️ Suggested Labels
🎯 Expected Outcome
A production-style project lifecycle management page with:
🏷️Labels
NSoC26FrontendFeatureenhancement🔗 Related Issues
Closes #20