Will this technique work with Custom UI and just including the localization data in the static public folder?
I don’t know @jeffryan.
client-side-ui-kit
was the initial name of what we know now as ui kit 2
.
As for Custom UI, it a self contained React build.
Don’t know the path for a public
folder hosting the translation files.
If you try, I’m interested in the results
Using Custom UI, you can still get the current locale using
import { view } from '@forge/bridge'
const context: FullContext = await view.getContext()
const locale = context.locale
and maybe inject the locale to get the localized strings.
2 Likes