Remove expression UUIDs from metadata section of a source file

[4e6]

Goal

• Remove IdMap from source file. #9257

This ticket describes the second part of #9257 tasks. The metadata section currently contains two types of information:

• node metadata like position, color, and/or widget metadata
• identification of expressions (and nodes) for communication with the engine via the LS protocol

The goal of this issue is to deal only with UUIDs of expressions where persistence isn't needed. The goal isn't to remove the whole META-DATA concept, but make the section significantly smaller.

Current Situation

The rumor has it that for a less than hundred lines .enso file the size of META-DATA section can grow significantly over 100KB - mostly because of storing UUIDs for all the expressions in the program, not just UUIDs for operatorXyz assignments.

The Plan

To quote 9257 comment:

Once #7954 is implemented ... then the Y.js based AST is hosted in the same process as the engine ... when there is an AST change that modifies the source code we traverse the AST and recompute ranges (offset, line, column) of expressions and nodes that _have an UUIDs attribute in the AST. A change in the source code always comes with new ranges. All of that is done synchronously, keeping UUIDs and their spans in sync.

Tasks

Preview Give feedback

1. traverse the AST and recompute ranges for elements with UUID attribute - let's call it dynamic UUID range information
2. provide the dynamic UUID range information to engine together with the source code change (probably by extending the LS TextEdit message)
3. use the dynamic UUID range information when parsing or while performing TreeToIr together with META-DATA section in the source file - e.g. merge those two
4. modify IDE to avoid storing UUIDs of expressions in the META-DATA section and just provide them via dynamic UUID range information
5. identify expressions in messages between GUI and Engine by both sources of UUIDs - e.g. by META-DATA section and dynamic UUID range information

TL;DR

• use dynamic UUID range information where persistence is not needed
• keep persistent information (where visualization is attached, what is the type of expression, etc.) in the META-DATA section as so far

[enso-bot]

Dmitry Bushev reports a new STANDUP for today (2024-06-06):

Progress: Started working on the task. A call with the gui team to discuss the plan for removing the IdMap. Started working on updating the Language Server API. Added an optional IdMap parameter to the textEdit message. Fixed an issue with refactor/renameProject request to support arbitrary project names. It should be finished by 2024-06-14.

Next Day: Next day I will be working on the #10182 task. Continue working on the task

[enso-bot]

Dmitry Bushev reports a new STANDUP for today (2024-06-07):

Progress: Continue working on the task. Updated Docker image adding a ydoc port argument for customization in the Cloud environment. Updated the language server API text/applyEdit method. Started updating the parser logic by resolving external ids in locations. It should be finished by 2024-06-14.

Next Day: Next day I will be working on the #10182 task. Continue working on the task

[enso-bot]

Dmitry Bushev reports a new STANDUP for today (2024-06-10):

Progress: Continue working on the task. Updated the textEdit request handling logic to propagate the IdMap. Updated the interactive compilation logic to handle the IdMap. Implemented the JSON serialization of IdMap. It should be finished by 2024-06-14.

Next Day: Next day I will be working on the #10182 task. Continue working on the task

[enso-bot]

Dmitry Bushev reports a new STANDUP for yesterday (2024-06-11):

Progress: Continue working on the task. Added backward-compatible JSON serialization for IdMap. Added JSON-RPC language server test. Fixed issue with Jsoniter serialization of IdMap It should be finished by 2024-06-14.

Next Day: Next day I will be working on the #10182 task. Continue working on the task

[enso-bot]

Dmitry Bushev reports a new STANDUP for yesterday (2024-06-12):

Progress: Continue working on the task. Added runtime test checking the IdMap propagation. Trying to fix the mapExpressions method of IR to make it useable with IdMap propagation. It should be finished by 2024-06-14.

Next Day: Next day I will be working on the #10182 task. Continue working on the task

[enso-bot]

Dmitry Bushev reports a new STANDUP for today (2024-06-13):

Progress: Continue working on the task. Added IdMap to a runtime module. Updated the logic that updates the internal module state. Fixed the runtime test with IdMap. Debugging the TreeToIr changes that make some runtime tests to fail. It should be finished by 2024-06-14.

Next Day: Next day I will be working on the #10182 task. Continue working on the task

[enso-bot]

Dmitry Bushev reports a new STANDUP for today (2024-06-14):

Progress: Continue working on the task. Fixed the runtime tests. Cleaned up and undrafted the PR. Implemented asynchronous Ydoc startup in the language server. It should be finished by 2024-06-14.

Next Day: Next day I will be working on the #10182 task. Continue working on the task