debug: coderabbit AI suggestions debugging

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,46 @@
+---
+name: Bug Report
+about: Report unexpected behavior or errors in the CoSA Student Database
+title: "Bug: [Short Description]"
+labels: bug
+assignees: ''
+---
+
+## 🐞 Describe the Bug
+*A clear, one-sentence summary of the issue.*  
+Example: "Admin users get a 403 error when trying to delete a student record."
+
+---
+
+## 🔍 Steps to Reproduce
+1. Go to '...'
+2. Click on '....'
+3. Enter '....'
+4. See error
+
+**Example:**
+1. Log in as an administrator.
+2. Navigate to the 'All Students' page.
+3. Click the 'Delete' button on any student row.
+4. A "Forbidden" error alert appears.
+
+---
+
+## ✅ Expected vs 🚫 Actual Behavior
+- **Expected:** What should happen?  
+  Example: "A confirmation modal should appear, and the student should be deleted upon confirmation."
+- **Actual:** What happens instead?  
+  Example: "A 403 Forbidden error is shown, and the student record remains."
+
+---
+
+## 📸 Screenshots & Evidence
+*(Please attach any relevant details)*  
+- [ ] Screenshot(s) of the error message or incorrect UI  
+- [ ] Console errors (Press F12 → Console tab)  
+- [ ] Network logs (Press F12 → Network tab, showing the failed request)  
+- [ ] Screen recording (if the bug involves a complex interaction)
+
+**Console Error Example:**
+```bash
+POST https://api.studentdb.com/students/delete/123 403 (Forbidden)

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,14 @@
+#Issue Template Configuration
+# This file configures the issue template chooser and adds helpful information
+
+blank_issues_enabled: false
+contact_links:
+  - name: Discord Community
+    url: https://discord.gg/hQFhv2t4
+    about: Join our Discord server to discuss issues, get help, and connect with other contributors.
+  - name: Documentation
+    url: https://github.com/OpenLake/Student_Database_COSA/blob/main/README.md
+    about: Check our README and documentation for setup instructions and project information.
+  - name: Known Issues
+    url: https://github.com/OpenLake/Student_Database_COSA/issues
+    about: Check if your issue has already been reported by browsing existing bug reports.

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,99 @@
+---
+name: " Documentation"
+about: Report missing, outdated, or unclear documentation
+title: "Docs: [Brief Description]"
+labels: "documentation"
+assignees: ""
+---
+
+##  Documentation Issue
+<!-- What documentation needs attention? -->
+**Type of Issue:**
+- [ ] Missing documentation
+- [ ] Outdated documentation
+- [ ] Unclear/confusing documentation
+- [ ] Incorrect documentation
+- [ ] Broken links
+
+---
+
+##  What Documentation?
+<!-- Be specific about which documentation is affected -->
+**Documentation Location:** [e.g., README.md, CONTRIBUTING.md, API docs, code comments]
+
+**Specific Section:** [e.g., "Installation section", "API reference for /users endpoint"]
+
+**Current State:** [Describe what's currently there or missing]
+
+---
+
+##  What's Missing or Wrong?
+<!-- Detailed description of the documentation issue -->
+**Problem:** [Describe the specific documentation issue]
+
+**Example:**
+- "The installation instructions don't mention required Node.js version"
+- "The API endpoint documentation is outdated and shows wrong parameters"
+- "Code examples are incomplete and won't run"
+
+---
+
+## Expected Documentation
+<!-- What should the documentation say/include? -->
+**What it should say:** [Describe what the correct documentation should include]
+
+**Proposed Content:** [If you know what should be documented, provide the content]
+
+**Examples/Screenshots:** [If applicable, provide examples or screenshots]
+
+---
+
+##  Target Audience
+<!-- Who is this documentation for? -->
+- **Primary Users:** [Developers/Contributors/End Users/API Consumers]
+- **Skill Level:** [Beginner/Intermediate/Advanced]
+- **Use Case:** [First-time setup/API integration/Contributing/Troubleshooting]
+
+---
+
+##  Related Resources
+<!-- Links to related documentation or issues -->
+- **Related Documentation:** [Links to related docs]
+- **Related Issues:** #[issue-number]
+- **External Resources:** [Links to external documentation that could be referenced]
+
+---
+
+##  Impact Assessment
+<!-- How does this affect users? -->
+- **Impact:** [High/Medium/Low - e.g., "High - prevents new contributors from getting started"]
+- **Affected Users:** [New contributors/Existing developers/API consumers]
+- **Frequency:** [How often do users encounter this issue?]
+
+---
+
+## Proposed Solution
+<!-- If you have ideas for how to fix this -->
+**Suggested Fix:** [Describe how you think this should be addressed]
+
+**Willing to Contribute:** [Yes/No - Are you willing to help write the documentation?]
+
+**Additional Notes:** [Any other context or suggestions]
+
+---
+
+##  Screenshots (if applicable)
+<!-- Show current documentation vs what it should look like -->
+| Current | Proposed |
+|---------|----------|
+| [Screenshot of current docs] | [Screenshot or description of improved docs] |
+
+---
+
+##  Community & Support
+Need help with documentation or want to discuss improvements?  
+Join our Discord 👉 [Student Database COSA Discord](https://discord.gg/hQFhv2t4)
+
+---
+
+** Tip:** Good documentation makes the project more accessible to everyone!

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,74 @@
+---
+name: " Feature Request"
+about: Suggest an idea for the CoSA Student Database
+title: "Feat: [Brief Description]"
+labels: "enhancement"
+assignees: ''
+---
+
+### Pre-submission Checklist
+- [ ] I have searched the [existing issues](https://github.com/OpenLake/Student_Database_COSA/issues) to ensure this feature has not already been requested.
+---
+
+##  Problem Statement
+**Current Issue:** [Describe the pain point or limitation in the current application]
+
+**Example:** "As an admin, it's time-consuming to manually export a list of students belonging to a specific club for reporting purposes. I have to filter and then copy-paste the data."
+
+---
+
+##  Proposed Solution
+**Solution:** [Provide a detailed description of the proposed feature]
+
+**Example:** "Add a 'Export to CSV' button on the student list page. When a filter is active (e.g., filtering by a club), clicking this button should download a CSV file containing only the filtered students' data, including their name, ID, and club positions."
+
+**Technical Notes (optional):** [API changes, database needs, third-party libraries, etc.]
+
+---
+
+##  Alternatives Considered
+1.  **Alternative A:** [Description of the alternative + why it's not the best choice]
+2.  **Alternative B:** [Description of the alternative + why it's not the best choice]
+
+---
+
+##  Mockups & Visual Examples
+-   [ ] Attach a sketch, mockup, or screenshot.
+-   [ ] Link to similar features in other applications.
+-   [ ] Provide Figma/design links.
+
+**Example References:**
+-   Similar export feature in Google Sheets.
+-   Design inspiration for the button style from [Link to design system].
+
+---
+
+##  Impact Assessment
+-   **Target Users:** [e.g., Admins, Club Coordinators, All Users]
+-   **Value Proposition:** [e.g., Saves time on reporting, reduces manual errors, improves data accessibility]
+-   **Usage Frequency:** [Daily / Weekly / Monthly / Ad-hoc]
+-   **Priority:** [Critical / High / Medium / Low]
+
+---
+
+## Success Metrics
+-   [ ] Metric 1: [e.g., "The 'Export to CSV' feature is used at least 10 times per week by admins."]
+-   [ ] Metric 2: [e.g., "Reduction in manual data copy-paste requests by 80%."]
+-   [ ] Metric 3: [e.g., "Positive feedback from at least 5 admin users within the first month."]
+
+---
+
+## Implementation Considerations
+-   **Estimated Complexity:** [Simple / Medium / Complex]
+-   **Dependencies:** [e.g., Requires the filtering logic to be stable first, see issue #...]
+-   **Breaking Changes:** [Yes/No - Will this change require data migration or affect existing API users?]
+
+---
+
+##  Additional Context
+-   **Related Features:** #[issue_number]
+-   **User Research:** [e.g., "This was requested by three different club coordinators during our last meeting."]
+
+---
+
+** Tip:** The more detailed your proposal, the better we can evaluate and implement it!

.github/ISSUE_TEMPLATE/style_enhancement.md

@@ -0,0 +1,74 @@
+---
+name: "Style Enhancement"
+about: Suggest UI/UX or design improvements for the CoSA Student Database
+title: "Style: [Brief Description]"
+labels: "style enhancement"
+assignees: ''
+---
+
+##  Current Style Issue
+**Problem:** [Describe the UI/UX or styling issue]
+
+**Location:** [Specific page/component - e.g., "Student List Table", "Login Form", "Navigation Bar"]
+
+---
+
+##  Proposed Style Changes
+**Suggested Changes:** [Improvements to typography, spacing, colors, layout, responsiveness, animations, etc.]
+
+**Technical Notes:** [e.g., Target CSS classes, React components, media queries, CSS variables]
+
+**Design Rationale:** [Why these changes will improve usability, readability, or overall user experience]
+
+---
+
+## Alternatives Considered
+1.  **Alternative A:** [Description of the alternative + why it's less ideal]
+2.  **Alternative B:** [Description of the alternative + why it's not the best choice]
+
+---
+
+##  Mockups & Visual References
+-   [ ] Attach a Figma/Sketch link or a screenshot
+-   [ ] Link to a similar UI in another application for inspiration
+-   [ ] Create a simple before/after comparison image
+
+**Visual Examples:**
+-   **Current:** [Description of current look, or a screenshot]
+-   **Proposed:** [Mockup or description of the new look]
+-   **Inspiration:** [Link to a design or app you admire]
+
+---
+
+##  Impact on UI/UX
+-   **Target Users:** [All users / Mobile users / Desktop users / New users]
+-   **Value:** [Better readability, smoother navigation, improved accessibility, modern look, etc.]
+-   **Accessibility Impact:** [How does this affect screen readers, keyboard navigation, color contrast, etc.?]
+-   **Responsive Considerations:** [How should this look on mobile, tablet, and desktop screens?]
+
+---
+
+##  Style & Component Consistency
+-   **Colors:** [Does this use the existing color palette/variables?]
+-   **Typography:** [Does this align with the established font sizes and weights?]
+-   **Spacing:** [Does this follow the current spacing conventions?]
+-   **Components:** [Is this consistent with the style of existing React components?]
+
+---
+
+##  Implementation Details
+-   **Complexity:** [Simple / Medium / Complex]
+-   **Files to Modify:** [List of CSS/JS/Component files that might need changes]
+-   **Dependencies:** [Are any new libraries (e.g., for animations) needed?]
+-   **Breaking Changes:** [Will this style change negatively affect any existing components?]
+
+---
+
+##  Additional Context
+-   **Related Issues:** #[issue_number]
+-   **Technical Constraints:** [e.g., Browser compatibility, performance considerations]
+-   **User Feedback:** [Have any users complained or made requests related to this UI?]
+
+---
+
+** Tip:** Great design improves user experience and makes the app more professional and enjoyable to use!