[ALOY-1719] Split out Alloy monolith into separate packages
| GitHub Issue | n/a |
|---|---|
| Type | Epic |
| Priority | None |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Tooling |
| Labels | n/a |
| Reporter | Ewan Harris |
| Assignee | Unknown |
| Created | 2020-02-13T17:17:11.000+0000 |
| Updated | 2020-03-09T11:20:45.000+0000 |
Description
Description
The Alloy package is currently a monolithic package that contains everything: * CLI * Parser/compiler * Runtime dependency code (underscore, backbone, moment) * Samples, lots and lots of samples Separating these components out allows the following benefits: * Allow for easier use in projects that need to parse alloy code, such as the webpack alloy-loader and potentially the language server * Allow testing the parser/compiler in isolation separately to the compile command greatly reducing our CI times (in theory) * Identify work the compiler does that we can potentially move to the SDK (such as the optimisations done in TIMOB-27167) and reduce the amount of work done in AlloyComments
No comments