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'd be very interested in seeing support for multiple distributions being consumed in an application. Our particular use case, and I'm sure many others will have this, is that we are maintaining shared libraries for re-usable components and plugins. These need translations as everything else and our applications are using a i18next library to provide said translations.
It would be a great benefit if we could set up the otaClient like new OTAClient([dist1, dist2]) to fetch both the shared library translations and the given application project translations.
Hope this might trigger some discussions and maybe a solution. Thanks!
T
The text was updated successfully, but these errors were encountered:
I'm afraid this is not possible with the current OTA client API design. We have methods that work with the current distribution and return the details about that distribution. For example getHash, getManifestTimestamp, listLanguages, etc. Allowing multiple distributions will break them, overcomplicate things, and create more edge cases to handle (duplicate keys, available languages, etc.).
I would suggest creating a wrapper on your side that can initialize as many OTAClient as needed and manage the received content from these distributions. Then, expose the downloaded data in the format that best suits your needs.
Hi!
I'd be very interested in seeing support for multiple distributions being consumed in an application. Our particular use case, and I'm sure many others will have this, is that we are maintaining shared libraries for re-usable components and plugins. These need translations as everything else and our applications are using a i18next library to provide said translations.
It would be a great benefit if we could set up the otaClient like new OTAClient([dist1, dist2]) to fetch both the shared library translations and the given application project translations.
Hope this might trigger some discussions and maybe a solution. Thanks!
T
The text was updated successfully, but these errors were encountered: