Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SemanticTokensOptions definition #47

Open
joyme123 opened this issue Aug 7, 2023 · 2 comments · May be fixed by #49
Open

SemanticTokensOptions definition #47

joyme123 opened this issue Aug 7, 2023 · 2 comments · May be fixed by #49

Comments

@joyme123
Copy link

joyme123 commented Aug 7, 2023

SemanticTokensOptions is defined as follow in Semantic Token

export interface SemanticTokensOptions extends WorkDoneProgressOptions {
	/**
	 * The legend used by the server
	 */
	legend: SemanticTokensLegend;

	/**
	 * Server supports providing semantic tokens for a specific range
	 * of a document.
	 */
	range?: boolean | {
	};

	/**
	 * Server supports providing semantic tokens for a full document.
	 */
	full?: boolean | {
		/**
		 * The server supports deltas for full documents.
		 */
		delta?: boolean;
	};
}

but in this repo, SemanticTokensOptions lack of legend, range and full fields

// SemanticTokensOptions option of semantic tokens provider server capabilities.
//
// @since 3.16.0.
type SemanticTokensOptions struct {
	WorkDoneProgressOptions
}
@Alfus
Copy link

Alfus commented Nov 3, 2023

I've run into this issue as well.

@gamebox
Copy link

gamebox commented Jan 1, 2024

I am also suffering for this issue, and it seems I can't convince the client (neovim) to issue semanticTokens requests without them.

@gamebox gamebox linked a pull request Jan 1, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants