microsoft/language-server-protocol

Need examples of overLappingTokenSupport and multilineTokenSupport

Open

#1,129 opened on Nov 5, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)HTML (12,810 stars) (956 forks)batch import
clarificationhelp wantedsemantic tokens

Description

I added two capabilities to the spec:

	/**
	 * Whether the client supports tokens that can overlap each other.
	 */
	overlappingTokenSupport?: boolean;

	/**
	 * Whether the client supports tokens that can span multiple lines.
	 */
	multilineTokenSupport?: boolean;

Originally posted by @dbaeumer in https://github.com/microsoft/language-server-protocol/issues/1077#issuecomment-721653729

The example in the documentation doesn't address the above. An example would be good.

Contributor guide

Tech stack
None
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of LSP specificationFamiliarity with semantic tokens
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Review the existing documentation for semantic tokens in the LSP specification. The overlappingTokenSupport and multilineTokenSupport capabilities were added in issue #1077. Look at the specification file (likely in the 'specification' folder) and the existing examples for other capabilities to understand the format. Then add examples for these two capabilities in the appropriate section, following the same style.
Need examples of overLappingTokenSupport and multilineTokenSupport · microsoft/language-server-protocol#1129 | Good First Issue