mirror of https://github.com/enso-org/enso.git synced 2024-12-23 06:01:37 +03:00

History

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
..
src	Cleaning up YAML parsing in preparation for `circe-yaml` removal (#10309 )	2024-06-20 13:07:54 +00:00
README.md	Add a markdown style guide (#1022 )	2020-07-21 13:59:40 +01:00

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

src Cleaning up YAML parsing in preparation for circe-yaml removal (#10309 ) 2024-06-20 13:07:54 +00:00

README.md Add a markdown style guide (#1022 ) 2020-07-21 13:59:40 +01:00

README.md

Enso Language Server

The Enso Language Server is responsibile for providing a remote-communication protocol for the runtime, exposing many of its features to the users. In addition it provides the backing service for much of the IDE functionality associated with the language. It encompasses the following functionality:

Introspection Services: Giving clients the ability to observe information about their running code including values, types, profiling information, and debugging.
Code Execution: The ability for clients to execute arbitrary Enso code in arbitrary scopes. This can be used in conjunction with the above to provide a REPL with an integrated debugger.
Code Completion: Sophisticated completion functionality that refines suggestions intelligently based on context.
Node Management: Tracking and providing the language server's internal node representation of the Enso program.
Code Analysis: Analysis functionality for Enso code (e.g. find usages, jump-to-definition, and so on).
Refactoring: Refactoring functionality for Enso code (e.g. rename, move, extract, and so on).
Type Interactions: Features for type-driven-development that allow users to interact with the types of their programs.