Final translator integration and bug fixes#59
Merged
Conversation
|
I checked the branch and the translation flow is working properly now. The [object Object] issue is fully resolved, and the backend returns a clean string instead of a wrapped response. The connection to the GPU translator service is also working as expected. |
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.
Summary
This PR finishes the translation feature and fixes the remaining issues in both the backend and frontend. The translator service is now fully connected to NodeBB and translated messages display correctly.
Backend Updates
Connected the translator API at crs-17313-debug-divas-gpu.qatar.cmu.edu:8080.
Fixed the issue where NodeBB received [object Object] instead of a string.
Testing
Before: non-English messages showed [object Object].
After: German messages are detected correctly and display the proper translated text.
Screenshots included below show the issue before and the correct behavior after.