Description
To proof the concept of delivering information from the engine to the IDE(s) via Ydoc structures is viable, let's prototype delivery of expression updates. To do following tasks are needed:
### Tasks
- [ ] Design changes to the Ydoc AST structures, so they contain [expression updates](https://github.com/enso-org/enso/blob/5afcb15ff2635f6701afaee2a3927f43fa4f26ed/docs/language-server/protocol-language-server.md#expressionupdate)
- [x] Implement a way to launch a [GraalVM Insight](https://www.graalvm.org/latest/tools/graalvm-insight/) script in the `EnsoContext` created by `language-server` and expose Ydoc AST to it - #11385
- [ ] Use Insight script to update the Ydoc structures with _expression update_ information
- [ ] Change the IDE to use this information instead of the one obtained via [language server protocol](https://github.com/enso-org/enso/blob/5afcb15ff2635f6701afaee2a3927f43fa4f26ed/docs/language-server/protocol-language-server.md)
If this proofs viable, then we can continue delivering visualizations via the AST mechanism.
Metadata
Metadata
Assignees
Type
Projects
Status