Longer term it would be good to move this to an issue on the main app repo, however will likely need to wait until larger refactor to the way deployment configs are parsed (had been started in some https://github.com/IDEMSInternational/parenting-app-ui/pull/2086, so would be good to also reference the issue there), and also might be a bit tricky to handle cases where the child deployment may still want to read from the parent deployment folder.
It would be good to also check at the same time whether the source_strings_path property is actually used anymore, so should probably be removed (issue to create on main repo), and other generated config properties that appear to possibly be pointing to the wrong location
Longer term it would be good to move this to an issue on the main app repo, however will likely need to wait until larger refactor to the way deployment configs are parsed (had been started in some https://github.com/IDEMSInternational/parenting-app-ui/pull/2086, so would be good to also reference the issue there), and also might be a bit tricky to handle cases where the child deployment may still want to read from the parent deployment folder.
It would be good to also check at the same time whether the
source_strings_path
property is actually used anymore, so should probably be removed (issue to create on main repo), and other generated config properties that appear to possibly be pointing to the wrong locationOriginally posted by @chrismclarke in https://github.com/IDEMSInternational/plh-teens-app-tz-content/issues/9#issuecomment-1888107498