-
Notifications
You must be signed in to change notification settings - Fork 799
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
Document Highlight spec unclear and possibly wrong #32
Comments
@smarr to which code base are you referring to with export interface DocumentHighlightProvider {
provideDocumentHighlights(model: editor.IReadOnlyModel, position: Position, token: CancellationToken): DocumentHighlight[] | Thenable<DocumentHighlight[]>;
} Is this from the Monaco editor? |
if i try to implement the document highlight in the node example it wants me to do something like+
|
and it is in monaco.d.ts as well |
any news on this? |
@cdietrich sorry vacation time here, delays are to be expected... |
@dbaeumer at other places you use |
Good catch. Fixed it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As discussed and noted in issue #18, there might be something wrong with the document highlight spec (see #18 (comment) and below).
Furthermore, the wording of the spec does not tell me what this feature is for (apparently something like 'mark occurrences'), so, it's unclear to me at the moment.
The distinction between read/write/text is unclear to me, too. What is it useful for exactly? (Would be good to know so that I know how to map it to my language.)
And, the vscode apparently also expects a collection of elements as return value, as noted by @cdietrich:
The text was updated successfully, but these errors were encountered: