forked from CMU-17313Q/cmu-17313q-f24-nodebb-f24-NodeBB
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Bug Archive Feature in Admin Dashboard - User Story 2 #53
Open
galishaq
wants to merge
56
commits into
f24
Choose a base branch
from
sprint2
base: f24
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
…mittid feedback to the admin only
…he bug archive bug to handle bug retrval and rendering in the bug archive page
…submitted bugs/feedback in the admin dashbored
…ly link it with the js file of the bug-archive
…he bug data to the server and stores it in the database
… when the page is loaded or when the submit button is clicked
… the admin dashbored
… its seding the content to the the bug archive page in the admin dashboared
…shboared/bug-archive.tpl
…hboared in admin.js file
…rm to the admin page in sidebar-left.tpl & admin.js
…bmitBug and getBugArchive to handle the retival and rendering of the bugs correctly
…mit the bug/feedback without being an admin
…orm submission correctly
…ashboared to define the route GET /api/admin/dashboard/bug-archive in schema docs
…rm.js to test the functionality of the test
…ared in the new branch auto-test-us2 under the path test/bug-archive.js
…test the bug archive page in the admin dashboared
…e new branch auto-test-us2 under the path test/bug-archive.js
…e sidebar-left in the new branch auto-test-us2 under the path test/bug-form.js
…t the bug form and the submit bug button in the left sidebar on the UI
This was
linked to
issues
Oct 20, 2024
Fixed the csrf token error and POST forbidden but now. I'm facing a new issue where the data is being sent to the bug archive page yet it's not being regcognized as data but rather as $ |
…nch which contains the submitting bugs feature logic Add Automated Tests for Bug/Feedback Form and Bug Archive Page - User Story 2
Hakaabi
approved these changes
Oct 20, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Impressive! looks good to me
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.
This pull request introduces the Bug Archive feature in the Admin Dashboard for User Story 2. The primary goal is to allow admins view all submitted bugs/feedbacks through the dashboard. While the core functionalities are implemented, there are issues preventing the full user story from being completed due to a POST request being forbidden.
New Files Added:
Modified Files:
Current Issues for not completing the User Story :
While the feature components have been fully built and the correct routes are in place (which can be seen in the partial testing pull request), the form is not sending data to the archive due to an issue with the form submission process. POST requests for submitting bug reports are being blocked due to forbidden errors only when the data is being sent from the form submit button (Yet when I post it manually its working through the chrome index tool ). As a result, the form and bug archive are not fully connected, preventing the form data from being successfully submitted to the Bug Archive
resolves #17
resolves #43
resolves #44
resolves #45