[TIMOB-16341] CLI: Support defining Ti dependencies in modules
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2014-01-30T19:12:47.000+0000 |
| Affected Version/s | Release 3.2.0 |
| Fix Version/s | n/a |
| Components | CLI |
| Labels | n/a |
| Reporter | Jon Alter |
| Assignee | Chris Barber |
| Created | 2014-01-29T19:41:30.000+0000 |
| Updated | 2014-06-19T12:43:43.000+0000 |
Description
During build time, the CLI excludes Ti Classes that are not found in the app's js code. This is problematic when a module uses a class that is not used in any js code.
For example, the Brightcove module uses TiMediaVideoPlayerProxy class and it is necessary to have a line of code referencing
Ti.Media.createVideoPlayer so that class will be included in the build (see MOD-1628).
It would be very helpful if we could define the classes that are used in a module and have the build process include those classes without having to reference them in the js.
Hmm, isn't this what the metadata.json file is used for? Handling of the metadata.json file is not identical between iOS and Android, so we'd need to check if each are correct and if it solves your use case.
Sure is! How did I not know about this? Thanks [~cbarber]