Can't disable full document semantic tokens request

I try to disable providing semantic tokens for a full document. But when I edit document, semanticTokens.on() is allways trigger ,not semanticTokens.onRange().

codes:

connection.languages.semanticTokens.on((handler, token, workDoneProgress, resultProgress) => {
	const t = Date.now();
	try {
		// ...
	}
	finally {
		console.log(`semanticTokens.on, time: ${Date.now() - t}ms`);
	}
})
connection.languages.semanticTokens.onRange((handler, token, workDoneProgress, resultProgress) => {
	const t = Date.now();
	try {
		// ...
	}
	finally {
		console.log(`semanticTokens.onRange, time: ${Date.now() - t}ms, lines: ${handler.range.start.line} ~ ${handler.range.end.line}`);
	}
});
connection.client.register(SemanticTokensRegistrationType.type, {
	// ...
	range: true,
	full: false, // <------------ disabled
});

log:

semanticTokens.onRange, time: 342ms, lines: 0 ~ 94
semanticTokens.on, time: 1447ms
semanticTokens.onRange, time: 21ms, lines: 0 ~ 93
semanticTokens.on, time: 2206ms
semanticTokens.on, time: 1419ms
semanticTokens.on, time: 1382ms
semanticTokens.on, time: 1435ms
semanticTokens.on, time: 1375ms
semanticTokens.on, time: 1372ms
semanticTokens.on, time: 1916ms
semanticTokens.on, time: 1937ms

[dbaeumer]

The spec can’t force all clients to handle range only. There are clients out there that simply can’t implement this. This is why the spec behaves that way and it does in all other cases. So it is not a wrong design. It is on purpose!

This being said VS Code does support it and there was a problem in the library that didn’t call range in the absence of full. I fixed that.

[johnsoncodehk]

I will try again with npm run symlink:testbed.