Skip to content

Update to use DebugConfigurationProvider #1062

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

Merged
merged 3 commits into from
Oct 26, 2017

Conversation

rkeithhill
Copy link
Contributor

Fix #1046
Fix warning in status bar about ThemeColor

This fix requires PSES PR 556 to eliminate one PSES cause of the debug adapter to crash.

Also npm generated a package-lock.json file which, from what I've read, should be checked in. I haven't included it in this PR - yet. Thoughts?

Also, I updated min VSCode version to 1.17.0. I'm not sure when the new DebugConfigurationProvider API was intro'd. I have tested with 1.17.2 and it works there so I'm reasonably confident it will work in 1.17.0. We might be able to reach back a bit further. We'd have to find out when this API was intro'd.

Fix #1046
Fix warning in status bar about ThemeColor

This fix requires PSES PR 556 to eliminate one PSES cause of the debug adapter to crash.

Also npm generated a package-lock.json file which, from what I've read, should be checked in.  I haven't included it in this PR - yet.  Thoughts?

Also, I updated min VSCode version to 1.17.0.  I'm not sure when the new DebugConfigurationProvider API was intro'd.  I  have tested with 1.17.2 and it works there so I'm reasonably confident it will work in 1.17.0.  We might be able to reach back a bit further.  We'd have to find out when this API was intro'd.
@rkeithhill rkeithhill requested a review from daviwil October 21, 2017 07:29
@rkeithhill
Copy link
Contributor Author

rkeithhill commented Oct 21, 2017

Hmm, set vscode engine min level to 1.16.0 and got this:

error TS2305: Module ''vscode'' has no exported member 'DebugConfigurationProvider'.

Maybe we just stick with a minimum of VSCode 1.17.0 then.

@rkeithhill rkeithhill force-pushed the rkeithhill/update-dbg-protocol branch from dc43a12 to b325257 Compare October 21, 2017 17:59
@daviwil
Copy link
Contributor

daviwil commented Oct 23, 2017

Yep, go ahead and add package-lock.json, it's new the new standard behavior in Node 8 I think.

I suppose my only concern here is whether we ship an update later this week (I'd like to) and if this will work in VS Code 1.16.0. Have you tried loading the built extension in that version to see if it works?

@rkeithhill
Copy link
Contributor Author

I bumped the version down to 1.16, pushed that but one of the builds failed. So I backed that change out.

@rkeithhill
Copy link
Contributor Author

I'll add the package-lock.json file as soon as I get home tonight.

Also update .gitattribtues to configure npm files to use LF since the newer version seems insistent about using LF.    See npm/npm#17161
@rkeithhill
Copy link
Contributor Author

Done.

@rkeithhill
Copy link
Contributor Author

For the record, it seems the API we need only exists in 1.16.0 in the vscode.proposed.d.ts typings file. In 1.17.0 the API appears in the vscode.d.ts file.

@daviwil
Copy link
Contributor

daviwil commented Oct 26, 2017

I just tried your changes in 1.17.2, they work great! Thinking about merging this now, anything else you needed to do?

@daviwil daviwil added this to the 1.5.0 milestone Oct 26, 2017
@rkeithhill
Copy link
Contributor Author

I think this one is ready to go.

@daviwil
Copy link
Contributor

daviwil commented Oct 26, 2017

Awesome, thanks a lot for fixing it!

@daviwil daviwil merged commit f944f4e into master Oct 26, 2017
@daviwil daviwil deleted the rkeithhill/update-dbg-protocol branch October 26, 2017 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

VSCODE- Insiders: Timed out waiting for the PowerShell extension to start
2 participants