enso/distribution/launcher
Hubert Plociniczak 114b3a5c5e
Cleaning up YAML parsing in preparation for circe-yaml removal (#10309)
The current implementation contains logic that should enable us to make some backward compatibility config changes.
At the same time, the logic is tightly integrated with circe's JSON library, which we want to eventually to get rid off.
Rather than trying to keep it somehow around and maintain via some hacks this PR proposes to ditch that logic completely as we currently have no use-case for such scenarios.

As a result, classes modelling YAML configs now don't have the extra fields and there is 1:1 correspondence.

Performance has also improved although that wasn't the main objective, yet. Follow up PR will attempt to replace `circe-yaml` with `snakeyaml` directly.

In preparation for #9113. Note that the dependency upgrade is necessary because it brings latest available `snakeyaml` (as part of `circe-yaml`).
2024-06-20 13:07:54 +00:00
..
THIRD-PARTY Cleaning up YAML parsing in preparation for circe-yaml removal (#10309) 2024-06-20 13:07:54 +00:00
.enso.portable Automate the Enso release process (#989) 2020-07-21 17:30:01 +01:00
README.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00

Enso CLI

Actionables for this file:

  • This is just a draft of the file that will be included inside the launcher distribution. It should be completed when the launcher is implemented.

Installation

The Enso distribution is portable, you can put this directory wherever you want on your system. For example you can put it at ~/.enso.

It is a good idea to add the bin directory to your system PATH so that you can run Enso just by typing enso in any directory.

Usage

Actionables for this section:

  • Fill in examples showing how to use the launcher.

Distribution structure

Actionables for this section:

  • This should explain the structure of enso distribution directory, based on the documentation.