Hi Tony,
Library should default to preferring any overrides from the custom directory, including for the strings.yaml file. Note though, a copy of the strings.yaml file
will not replace the original entirely. Only fields that exist in both files will be taken from the strings.yaml in the custom directory.
If none of your changes from the custom/strings.yaml file are coming through at all, Library may not have detected your strings.yaml override.
Two things can be tricky here:
- Library expects the override file to be named very precisely. It should be "strings.yaml" and directly inside the custom folder.
- When using Heroku, the provided config automatically nests the contents of the custom repo inside the custom folder. For example, your customization repo should look something
like this for use with the Deploy to Heroku button.
Does Library detect your custom/strings.yaml when running locally? This could help point more specifically to a Heroku vs customization config problem.
Hope that's helpful.
Isaac