[ALOY-1375] Alloy extract-18n --apply writes to wrong strings.xml in Alloy 1.8.1
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2016-03-24T17:18:36.000+0000 |
| Affected Version/s | alloy 1.8.0, alloy 1.8.1 |
| Fix Version/s | Release 5.2.1, alloy 1.8.2 |
| Components | Tooling |
| Labels | n/a |
| Reporter | Stephen Feather |
| Assignee | Fokke Zandbergen |
| Created | 2016-03-24T04:00:49.000+0000 |
| Updated | 2016-03-24T19:12:36.000+0000 |
Description
Expectation
The expectation is that the extract-i18n command will write to at least app/i18n/{language}/strings.xmlReality
The extract-18n command writes to {project}/i18n/{language}/strings.xml which is in an alloy_generated folder in 1.8.1Comments
- Chris Barber 2016-03-24 I didn't forget about it because I never knew it existed. I'm not sure why the extract-i18n command exists.
- Fokke Zandbergen 2016-03-24 Thanks for catching this [~sfeather]! The fix is in. [~emerriman] I'll leave it up to you to decide if we bump the Alloy version before the CLI 5.2.1 release.
- Eric Merriman 2016-03-24 [~fokkezb] We are building a new CLI and unless something horrible happens will test for inclusion in 5.2.1.
- Feon Sua Xin Miao 2016-03-24 PR merged by Fokke
- Eric Wieber 2016-03-24 Verified fixed, using: MacOS 10.11.4 (15E65) Studio 4.5.0.201602170821 Ti SDK 5.2.1.v20160318225121 Appc NPM 4.2.4-2 Appc CLI 5.2.1-21 Alloy 1.8.2 Xcode 7.3 (7D175) The strings.xml file is now generated in the apps/i18n directory and correctly merged with an existing file.