Add some more tests around common ways to use constructor functions for new types, then start fixing the behavior for those cases. WIP, still broken in some cases.
Show all indices for a JS project in Index view
Fix handling of:
``` javascript
var x = new function() { this.y = \"red\"; }
```
to record the type as Function<x> - the same way we do for:
``` javascript
function x() { this.y = \"red\"; }
```
- Unwrap Function<x> types to just x for inferring types of constructors
- When properties are hung off the prototype property of a type, elevate those up in our index to be properties of the type.
- Add tests for adding properties to the prototype property of a type after the initial type's constructor has been defined.
If module.exports points at a constructed object, unwrap that constructor's return type as the type of the module.exports object.
- Handle nested property assignments using "this" in a constructor function.
- Handle assignments of properties to an object using element syntax (i.e. this.apis['customerevent'] = ...)
WIP on trying to better hanlde "bad" XMl where an attribute's value is unquoted and begins with a digit
TISTUD-6683 Gracefully handle invalid XML attribute values
- be able to handle unquoted attribute values that begin with digits in our scanner
- mark unquoted attribute values as parse errors and recover in our parser
- mark attributes with no value as parse errors and recover in our parser
Address review feedback
Merge pull request #224 from sgtcoolguy/TISTUD-6683

TISTUD-6683 Gracefully handle invalid XML attribute values
Merge pull request #222 from sgtcoolguy/TISTUD-6750

TISTUD-6750 Javascript indexing isn't aware of constructor functions for generating types