Localisation does not work when localisation files are in a project (sub)folder in the project.
The folder feature is very nice, as it allows structuring your project content.
however, it seems that the localisation feature does not find the localisaton files (xxxxx.strings) back when they are in a subfolder.
It would be nice if these files could be placed in a subfolder, to avoid that these clutter the project when a model is localised in many languages (as in our case) … Potentially by specifying the location in the project manifest?
Thanks for calling this out! We’ll think about how best to implement this 🙂
Thanks for reporting this. We have fixed it. In the next looker release (6.20), localization
.stringsfiles can be in the root or sub folders in your project.
When is 6.20 going to be available to the public?
I would love to give this a shot to see if it works for me!
@stijn! The release of Looker 6.20 is anticipated to be released September 18th.