Skip to content

Final translator integration and bug fixes#59

Merged
mhmansoo merged 4 commits into
mainfrom
feature/translation-frontend-p4-100
Nov 18, 2025
Merged

Final translator integration and bug fixes#59
mhmansoo merged 4 commits into
mainfrom
feature/translation-frontend-p4-100

Conversation

@mhmansoo
Copy link
Copy Markdown

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.

Screenshot 2025-11-16 at 9 35 10 PM Screenshot 2025-11-16 at 9 35 20 PM

@aalmuhan
Copy link
Copy Markdown

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.
The UI updates show the translated text immediately, and non-English messages are detected and processed correctly. The frontend changes keep the behavior consistent with the rest of the messaging components.

@mhmansoo mhmansoo merged commit 0ab11c5 into main Nov 18, 2025
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants