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 believe these are currently managed by manually ensuring that the strings are included in any complete set of deployment app strings for translation (@esmeetewinkel is that right?).
We may also want additional hardcoded strings in other contexts in the future, for example, see this discussion on #2788. So likely we want to gather all such strings on one place and find a general solution for including them all intranslations.
The text was updated successfully, but these errors were encountered:
What?
A limited number of hardcoded strings are included as default values in the app config:
open-app-builder/packages/data-models/app-config/globals.ts
Lines 10 to 15 in dab81ac
These strings should be integrated into the translation workflows somehow.
Another example of hardcoded strings is these navigation labels in the tour service:
open-app-builder/src/app/feature/tour/tour.service.ts
Lines 55 to 57 in f8d523b
I believe these are currently managed by manually ensuring that the strings are included in any complete set of deployment app strings for translation (@esmeetewinkel is that right?).
We may also want additional hardcoded strings in other contexts in the future, for example, see this discussion on #2788. So likely we want to gather all such strings on one place and find a general solution for including them all intranslations.
The text was updated successfully, but these errors were encountered: