[ALOY-1034] Alloy : Incorrect month value used in generated file names, e.g. migrations
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2014-05-30T18:08:03.000+0000 |
| Affected Version/s | Alloy 1.3.1 |
| Fix Version/s | Alloy 1.5.0 |
| Components | n/a |
| Labels | alloy-cli, alloy-generate, community, qe-manualtest |
| Reporter | Jeff Antram |
| Assignee | Tim Poulsen |
| Created | 2014-05-30T14:22:49.000+0000 |
| Updated | 2014-08-26T00:26:45.000+0000 |
Description
Generated migration filenames have the incorrect month value. (i.e. January = 0)
$ alloy generate migration MyCollection
Alloy 1.3.1 by Appcelerator. The MVC app framework for Titanium.
[INFO] Generated migration named 2014 *04* 301417826_MyCollection
Month should be 05 / May
Fixed in PR 403 https://github.com/appcelerator/alloy/pull/403
Jeff - Good catch and thank you for the pull request. Moving this to engineering as I can reproduce the issue with the provided test steps.
PR tested and merged
Verified fix on: Mac OSX 10.9.4 Appcelerator Studio, build: 3.4.0.201408210941 Titanium SDK build: 3.4.0.v20140813022514 Titanium CLI, build: 3.4.0-dev Alloy: 1.5.0-dev Used command alloy generate migration MyCollection and the file generated was named 201408260009768_MyCollection , 08 is the correct month value. Closing ticket.