1.0.1

First public release of MASCOT.

Known limitations in v.1.0.0

• MASCOT makes no differentiation between dirty and clean projects, and compiles the entire dependencies tree every time, which wastes time.
• No parallel compilation available. While Visual Studio Code's build tasks system does permit unrelated tasks to run in parallel, MASCOT does not leverage this, and always generates build tasks that are executed sequentially, even if they are unrelated. This also wastes time.
• The src, bin and lib folder names are assumed by MASCOT and cannot be changed. If an ActionScript project uses, e.g., projsrc for its source folder name, that will not be recognized by MASCOT as a valid project, and will be ignored.
• MASCOT does not currently recognizes couplings defined in MXML classes via custom MXML tags (by contrast, couplings defined in fx:Script sections are accounted for).
• MASCOT cannot detect couplings to classes that live in the global package, or live in another project but in the same package as the current class. The g_manual_dependencies argument/configuration directive can be used as a workaround, to manually couple such classes.
• There is no way to account for manual directives in the generated asconfig.json. MASCOT automatically generates one asconfig.json file per project, but if you want to add your own settings in-there, currently there is no way to preserve them.