You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand this is a feature request and questions should be posted in the Community Forum
I searched issues and couldn’t find anything (or linked relevant results below)
Problem
Fake folders like "Shared with me" (Google Drive / Photos) is currently hardcoded in Companion and returned to Uppy and therefore cannot be i18n in the client.
Not sure the best way to support i18n, but maybe leave name as undefined and have a separate field named something like specialFolderType which can then be i18n in the Uppy frontend? (maybe Uppy can set name to this i18n value when it receives a folder with specialFolderType from companion)
Agreed we should translate "Shared with me"/"Albums"/"Timeline".
The solution you described sounds good to me, given partialTreeFolder.data.name gets filled with the i18n value as soon as the file is fetched, making item.data.name always a string.
Initial checklist
Problem
Fake folders like "Shared with me" (Google Drive / Photos) is currently hardcoded in Companion and returned to Uppy and therefore cannot be i18n in the client.
uppy/packages/@uppy/companion/src/server/provider/google/drive/adapter.js
Line 174 in 46e6be8
Solution
Not sure the best way to support i18n, but maybe leave
name
as undefined and have a separate field named something likespecialFolderType
which can then be i18n in the Uppy frontend? (maybe Uppy can setname
to this i18n value when it receives a folder withspecialFolderType
from companion)see also #5275 (comment)
Alternatives
implement i18n in companion too and detect the client's language
The text was updated successfully, but these errors were encountered: