#34, #110 - suppress Intellisense in strings and comments#339
#34, #110 - suppress Intellisense in strings and comments#339MikhailArkhipov merged 19 commits intomicrosoft:masterfrom MikhailArkhipov:master
Conversation
DonJayamanne
left a comment
There was a problem hiding this comment.
Please ensure all files end with blank line.
Please install the EditorConfig extension for vscode, that'll help.
DonJayamanne
left a comment
There was a problem hiding this comment.
Please ensure all files end with blank line.
Please install the EditorConfig extension for vscode, that'll help.
|
Tough to review in the phone, however I failed to notice any test for this feature. I.e. disable intellisense when inside a string. I think we'll need that. Over all 👍 |
|
Yes Will do |
|
Do we have an issue(s) tracking this change? |
| @@ -0,0 +1,84 @@ | |||
| 'use strict'; | |||
|
|
|||
There was a problem hiding this comment.
Please rename file to types.ts (that'll be the standard going forward, documented in standards document)
There was a problem hiding this comment.
Ensure types.ts only contain interfaces. I.e. please move TextRange out into septate file
There was a problem hiding this comment.
Actually it is used as both interface and direct type (i.e. new TextRange). Types that are not normally used directly, are in separate files. So basically definitions is public surface.
| @@ -0,0 +1,131 @@ | |||
| 'use strict'; | |||
|
|
|||
There was a problem hiding this comment.
Please add Microsoft license header to all new files.
Also please remove use strict (not necessary)
There was a problem hiding this comment.
Can't find the license header sample, where is the template
There was a problem hiding this comment.
The official link is https://docs.opensource.microsoft.com/releasing/copyright-headers.html
src/test/autocomplete/base.test.ts
Outdated
| assert(vscode.window.activeTextEditor, 'No active editor'); | ||
| textEditor = editor; | ||
| for (let i = 0; i < positions.length; i += 1) { | ||
| vscode.commands.executeCommand<vscode.CompletionList>('vscode.executeCompletionItemProvider', |
There was a problem hiding this comment.
I don't think the tests will work. Theoretically this should fail. Since this is an async operation, we have to wait for this to complete.
In line 211, we're basically saying we're all done, when in fact the code in line 204 is still running, i.e. tests won't/shouldn't work.
You'll have to wait for executeCommand to complete as done in line 117.
You could build a list of promises and then use Promise.all() or other mechanism.. But we need to wait for the completion of each.
There was a problem hiding this comment.
@MikhailArkhipov this needs to be done.
src/test/index.ts
Outdated
| timeout: 25000, | ||
| retries: 3 | ||
| retries: 3, | ||
| grep: "Language.TextRangeCollection" |
There was a problem hiding this comment.
@MikhailArkhipov this needs to be done
|
And with that, @MikhailArkhipov is now the 19th most prolific contributor to the extension! 😄 |
Closes #34 , #110