[TIMOB-14310] Allow either the Code Analyzer or Static Code Analysis Engine to be extensible to 3rd Parties
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Low |
| Status | Closed |
| Resolution | Won't Fix |
| Resolution Date | 2016-08-30T17:20:14.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | n/a |
| Labels | n/a |
| Reporter | Stephen Feloney |
| Assignee | Eric Merriman |
| Created | 2013-06-20T17:41:55.000+0000 |
| Updated | 2017-06-27T23:28:00.000+0000 |
Description
Partners and customers should be able to add to our code analysis engines. Either the Dynamic Code Analyzer or our static code analysis. One or both of these engines should be extensible. We will never be able to provide all the functionality that customers want:
Ex. Security checks, performance analysis, code formatting, depth level of call stacks, etc...
So we should allow 3rd parties or customers to add to the rules engine. This will provide added value to the platform, plus add our open and extensible claims
Code processor is dead. In the new Titanium build pipeline we will expose the AST to hooks so they can perform some static analysis, but that's about as far as we'll go.
Closing ticket as Code processor is no longer supported.