Uh oh!
There was an error while loading. Please reload this page.
fix: replace deprecated translation methods - #6567
Conversation
mejo-
left a comment
There was a problem hiding this comment.
I didn't dive too deep into the changes, but a quick testing didn't work as expected. While the fake providers provided by the testing app worked, the providers provided by the translation app were not listed.
What I did to reproduce:
- Disable app
testing - Enable apps
assistantandtranslate - Run
occ translate:download-models
When I load the translation modal from the assistant menu with this PR applied, the dropdowns "translate from" and "translate to" are empty and don't provide any language. Maybe I missed something?
luka-nextcloud
commented
Nov 19, 2024
@mejo- As I understand, the assistant app cannot work without testing app (or AI provider apps). So, disabling testing app means disabling assistant and translation. So, I think the test case doesn't make sense to me. |
juliusknorr
commented
Nov 21, 2024
There is also translate2, not sure if just an addition or successor. translate doesn't implement the new API. @marcelklehr From an integration team perspective, is it work to keep both APIs available or is just going with the task processing API and ignoring the old translation API fine. |
luka-nextcloud
commented
Nov 21, 2024
In my opinion, we should go with the task processing API and ignore the old translation API since it might be complicated to maintain when keeping both APIs. |
We opted to implement neither forward nor backward compatibility for the old Translation API in TaskProcessing. The translate2 app only uses the TaskProcessing API, while the translate app uses the old Translation API. I'd recommend to transition to TaskProcessing directly if you don't need to support nc < 30, as the old Translation API is already deprecated and you will need to transition at some point. If it's too much work for you to add support for task processing, we can talk about adding forward and backward compatibility in server, but I'd rather avoid that. |
mejo-
commented
Nov 27, 2024
@luka-nextcloud I'm still unable to successfully test this using real translation providers. Did you test this with real providers, or just with the testing app? What I did:
Problems:
When opening the assistant modal directly in the header bar (not via Text), translation works as expected, so I guess there's something wrong with the implementation in Text. This is how the dropdowns for selecting languages in the translation modal via Text look in my tests: |
e879703 to
08e25e1Compareluka-nextcloud
commented
Dec 4, 2024
@mejo- I have tested with both apps |
marcelklehr
commented
Feb 10, 2025
Note: integration_openai also implements a translation provider |
max-nextcloud
commented
Feb 10, 2025
/backport! to stable31 |
marcelklehr
commented
Feb 10, 2025
Installed successulfy now. Translation menu entry in the AI menu doesn't do anything on click: |
juliusknorr
commented
Feb 12, 2025
I can share credentials for easier testing with the integration_openai provider, just ping me if needed |
max-nextcloud
commented
Feb 14, 2025
That looks like you did not compile it yet. Could you try again? We can also jump on a call next week to try it together. |
marcelklehr
commented
Feb 14, 2025
Yeah, let's do that :) |
marcelklehr
commented
Feb 24, 2025
notes from test with new build: On opening: when selecting a new "from language":
|
max-nextcloud
left a comment
There was a problem hiding this comment.
Tested this with @marcelklehr and the integration worked fine. There were two errors in the logs:
- When changing the
fromLanguagewhiletoLanguagewas not set yet - When clearing the
toLanguage'.
Both pointed to line 157 of Tranlate.vue. I'll propose a change that will fix them.
In addition it would be good to also clear the result when the fromLanguage is changed - to allow for a recomputation.
Other than that this looks fine. I'll approve so you can fix the remaining things and then merge @luka-nextcloud
Uh oh!
There was an error while loading. Please reload this page.
Signed-off-by: Luka Trovic <luka@nextcloud.com>
08e25e1 to
c87a4b8CompareCodecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@## main #6567 +/- ##
==========================================
+ Coverage 37.49% 37.51% +0.02%
==========================================
Files 943 933 -10 Lines 42501 42476 -25 Branches 1466 1456 -10 ==========================================
Hits 15935 15935 + Misses 25788 25773 -15 + Partials 778 768 -10 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
luka-nextcloud
commented
Mar 10, 2025
@mejo- Could you please give an approval if everything is okay? |
juliusknorr
commented
Mar 10, 2025
Lets get this in as @mejo- is unavailable |
@luka-nextcloud Can you double check that this is somehow covered with tests? We should add some if we don't have yet |
Max tested it and it worked for Marcel as well.
juliusknorr
commented
Mar 19, 2025
/backport to stable31 |


📝 Summary
🏁 Checklist
npm run lint/npm run stylelint/composer run cs:check)✔️ TODO