[TIMOB-13958] Code Processor: Reuse project validation mechanisms from the CLI
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-08-22T00:41:53.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2013 Sprint 17, 2013 Sprint 17 Tooling, Release 3.2.0 |
| Components | Code Processor |
| Labels | n/a |
| Reporter | Ingo Muschenetz |
| Assignee | Matt Langston |
| Created | 2013-05-22T21:24:18.000+0000 |
| Updated | 2014-02-04T01:09:18.000+0000 |
Description
Now that the code processor is a part of the CLI, we should reuse as much CLI code as possible when parsing projects. Doing things like SDK version matching, module version matching, project validation, platform validation, is currently done using custom code in the code processor (a by product of it originally being a separate product). Now that it's part of the CLI, the code processor should let the CLI do these operations.
In addition to increasing code reuse, it will put project validation at parity with the CLI, which it currently is not.
Upping the priority because the code processor is broken with the latest CLI changes, and this is how to fix it.
PR: https://github.com/appcelerator/titanium-code-processor/pull/230
To test: run the code analyzer on a Titanium app via 'ti analyze -p iphone --all-plugins' while using the latest (3.2.0) CLI (this will require a custom deployment of the CLI). Without this fix, the code processor will crash the CLI.
Verified functionally. Closing.