microsoft / microsoft/language-server-protocol

Read Only Range in source code

Open
#1,522 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request new request
Dominant language
TypeScript
Stars
13k
Forks
1k
Avg merge
6d 1h
Merged PRs (30d)
10

Description

Consider a domain specific language like this

event <name> happens <condition>

with an AST node like Event(name: string, condition: Expression) where possible domain specific insertions via auto completion or typing into the placeholder end up into something like ...

event hello-world happens when universe > 42

In this approach I would love that the editor user cannot modify the basic "keyword" template of event<name>happens <condition> but only modify the placeholders in the brackets. There most be however some way to wipe the whole template 😀. Recursive usage also, since when<expression> is again a template.

This is prior art in editors (at least JetBrains MPS is using this methodology) which to my little knowledge they call a projection.

If this is already supported, open/rejected or discussed and I missed it, my apologies in advance.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified in the issue. Begin by locating the protocol areas related to source ranges and editor edits, then review existing discussions about recursive read-only templates. Done would require an agreed protocol design and corresponding implementation and tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.