[ALOY-1715] The generated directories /i18n and /platform should be moved
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | High |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Tooling |
| Labels | n/a |
| Reporter | Creative |
| Assignee | Unknown |
| Created | 2016-08-01T12:42:29.000+0000 |
| Updated | 2020-01-30T16:44:23.000+0000 |
Description
After the patch which required you to move the folders
i18n and platform into /app, the legacy folders were being created after a build with one tag-file named alloy_generated.
This makes little sense and I suggest generating those files into the build directory since that is where they belong. Having more generated directories in the root of your project requires people to add more .gitignore rules
[~cbarber] like some of your input on this :)
This ticket is referring to the changes made in ALOY-1365. I get what you're saying. Generating the
i18nandplatformfolder in the root of your project is a hack. It's because the Titanium build only knows to look in the root of your project for those folders. Sadly, there is no way to hook into the build to modify this behavior. FWIW, we did add/i18nand/platformto the.gitignorefor new projects: https://github.com/appcelerator/alloy/blob/master/templates/two_tabbed/.gitignore#L3-L4. The bad news is we will not be fixing this in Alloy 1.x. The good news is we will totally fix this in Alloy 2! We're going to bring Alloy into the Titanium build and this means Alloy apps will benefit from the latest build features and speed improvements. Follow the ticket here \-\-> TIMOB-20341 <\-\-I certainly like the idea of integrating Alloy into the Titanium SDK, however it seems like a cumbersome task that is likely months away from completion. Then again, if there is no way to change this at the moment then I guess we'll have to wait for 2.0.