Uploaded image for project: 'Alloy'
  1. Alloy
  2. ALOY-1719

Split out Alloy monolith into separate packages

    Details

    • Type: Epic
    • Status: Open
    • Priority: None
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Tooling
    • Labels:
      None
    • Epic Name:
      Alloy Modularization

      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 Alloy

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              eharris Ewan Harris
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Backbone Issue Sync

                • Backbone Issue Sync is enabled for your project, but we do not have any synchronization info for this issue.

                  Git Integration