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
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
Some thought is needed here how multiple Tx projects would map to Github repositories...an initially simple implementation would be to refactor tx_config files as hashes, and allow for a list of them to be configured.
However this would add alot of complexity to the project setup 😞
@matthewjackowski and I talked about this offline. I mentioned we've added the tx.config file to our repository and download it on each deploy. I'm currently working on a txgh feature to support multiple git branches, which could benefit from being able to download the config from github on each request (imagine for example if you add a new resource to your branch and want txgh to track it).
This is an interesting point, I could how this could be useful for mobile projects that are cross platform codebases...since the localized strings between both Android and iOS versions of the same app will be largely the same (so multiple branch support here)...but also even though Tx supports multiple different resource file formats in one project...its still advantageous to segregate them (possible more for linguistic reasons or permissions rather than technical)...so multiple project support would be needed as well.
@cstclairtx after we add more flexibility to Txgh...it would be great to re-validate cross platform, mobile flows.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
No description provided.
The text was updated successfully, but these errors were encountered: