… TODO comments

…or writing to stream

Splits the definition generator into two submodules, one for parsing the externs and one for writing the definition file.

…inputs

Moves all function related to building the definition tree into a separate submodule. Furthermore, the entry-function in generateTypescriptDefinitions now accepts multiple input files and merges their definitions into one tree.

- Rename property indentationLevel of AbstractWriter class to just level to show it can be used for more than one purpose
- Mark namespaces at level 0 as ambient by using the declare keyword

Output normal type aliases as `type` declarations and type object strucutes as interfaces

Previously, the type expression was passed as-is from the `@implements` keyword. Now directly passes the name and throws if implements is not followed by a name expression.

If a class node's attributes define a base class and/or interface, append them to the class declaration when generating the output for the class node.

…egation

- Move type generation to separate module as it will get a bit bigger as well
- Fix a bug in the aggregation of static class members. The attribute type was ignored here.

- Implement python method generate_typescript_definition as part of the build process
- Call generateTypescriptDefinitions from python with the generated externs and all externs/shaka scripts
- Adjust entry of generateTypescriptDefinitions to match generateExterns

…structor

…definition tree

Shaka player classes that implement an interface with properties just specify the property with the @OverRide tag. TypeScript requires implemented properties to specify the type again, so we have to infer the types from the interface that is implemented.

This is required for TypeScript to automatically pick up the typing if shaka-player is imported from npm package

…teTypeDefinitions

Generates TypeScript compatible types based on the information found in the doc comments

- Fix typo (`FuncionType` => `FunctionType`=
- Use correct property for getting the return type (`this` instead of `returnType`)
- Write correct node (generated `functionNode` instead of `node`)

- Treat rest types as arrays
- Assert that arrays have at most one applied type
- If no type is specified, default to `any[]`
- Use `Type[]` instead of `Array<Type>` where suitable

This allowed any type that wasn't explicitly marked as nullable to be non-nullable, which should not be the case.

Mixed up the nullability here as well. Primitives should be non-nullable by default, non-primitives should be nullable by default.

Add an option to disable inference of nullability. Used by type aliases and generic applications.

Inferes types for properties and methods in classes and interfaces from the implemented / extended interface if not types are given.

Closure supports overwriting the param types without overwriting the return type of an implemented/extended method. Act accordingly.

…feature/generate-typescript-typedefs

…-player changes

…feature/generate-typescript-typedefs

… type information more obvious