Closed
Conversation
- Add resolve button to post actions in topic template - Implement client-side toggle functionality in resolve.js - Button displays green checkmark when resolved, gray circle when unresolved - Text shows 'Resolved' or 'Unresolved' state (hidden on mobile) - Position button to the left of reply button in post toolbar
…nd only admins are able to toggle it
Attaching the backend feature for the unresolved/resolved buttons done in the frontend.
…ed questions keep status for student view
…sting functionality so it remains
…it testing for general testing and edge casing
…when post is approved by TA/admin, done by fixing theme post list views and caching
…spring-26-yc26 into check-branch Merging user story 2 testing coverage branch into user story 3 implementation branch, to have single final version to build off of.
US 3 Working: Supported by Instructor feature + US2 Testing
… not updating after backend change. Added timestamp and identifier of who approved a post to database. Also added more error catching to prevent page getting stuck reloading.
Need to update my branch with the main branch.
- Add viewers button to post actions for admins/TAs only - Display eye icon with view count next to reply button - Only visible on main post (index 0) in announcements category - Dropdown shows list of students who viewed the announcement
- Create viewers.js module to handle viewer dropdown - Load and display student viewers when dropdown is opened - Generate mock viewer data for testing (backend TBD) - Track student views in console (frontend-only) - Only admins/TAs can see viewers, students cannot
- Import and initialize viewers module in topic.js - Enables viewers dropdown functionality on topic pages
- Style viewer list items with hover effects - Add dropdown shadow for better visual hierarchy
…4-frontend Deleted make-anon file since it is no longer needed.
US4 frontend + backend + permissions (for post-replies & topic-replies)
Updated user root
Updating my main with the remote repo's main
Add Docker config for application settings
Begin build for environment since nodebb isn't starting the build
Correct spelling of env
Corrected URL for access
Removed env section so docker doesn't manually run build
Merging my main with the remote main
Setup ci pipeline
Adding the translation UI components
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.
Objective
This PR completes the Project 4 translation integration by wiring our NodeBB frontend UI directly to our deployed Python Flask microservice.
Changes Made
TRANSLATOR_APIconstant insrc/posts/summary.js(and related client scripts) to point away from localhost and route traffic to our live Linux VM athttp://17313-team09.s3d.cmu.edu:5000.translatorApi.translatefunction to properly await and extract the actual JSON variables (data.is_englishanddata.translated_content) returned by our Flask service, rather than returning the hardcoded placeholder strings from the starter code.How to Test
Once this PR is merged and our GitHub Actions pipeline redeploys the NodeBB instance to the VM, reviewers can test the full pipeline:
Dies ist eine Nachricht auf DeutschThis is a German message.Note to Reviewers
Since this relies on our Python microservice, please ensure the
tmuxsession running the Flask app on port 5000 of our VM is active if you encounter any network timeout errors!