-
Notifications
You must be signed in to change notification settings - Fork 676
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
Consume the completion trigger character API #1776
Conversation
Also take a dependency on version 1.17 where it was added
package.json
Outdated
@@ -1360,7 +1358,16 @@ | |||
"request": "attach", | |||
"processId": "${command:pickProcess}" | |||
} | |||
] | |||
], | |||
"windows": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why these got added. Presumably they can be removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove these. Otherwise, they'll break the debugger.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we want to take this into master yet. At least, not until 1.17 is the stable VS Code release. Otherwise, we won't be able to ship.
package.json
Outdated
@@ -1360,7 +1358,16 @@ | |||
"request": "attach", | |||
"processId": "${command:pickProcess}" | |||
} | |||
] | |||
], | |||
"windows": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove these. Otherwise, they'll break the debugger.
@DustinCampbell Right--I was going to ask you if you if we had a different branch that tracked the latest insiders build (or something). |
Also cc @piotrpMSFT and @jonsequitur in case they're interested. |
We don't have a different branch as we haven't been on the bleeding edge with VS Code APIs yet. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to go ahead and merge this. We've got an OmniSharp release coming in shortly that this will work with.
Fixes #146 |
Thanks @DustinCampbell |
For some reason, CI is hung for this PR. So, I went ahead and built and ran tests on my machine. |
Also take a dependency on version 1.17 where it was added and request to trigger completion on space.