Skip to content
This repository has been archived by the owner on Oct 2, 2021. It is now read-only.

Add support for address param in launch config that allows remote debugging #50

Merged
merged 1 commit into from
Jun 21, 2016

Conversation

nojvek
Copy link
Contributor

@nojvek nojvek commented Jun 21, 2016

No description provided.

@msftclas
Copy link

Hi @nojvek, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!


It looks like you're a Microsoft contributor (Manoj Patel). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@nojvek
Copy link
Contributor Author

nojvek commented Jun 21, 2016

cc @roblourens @auchenberg

@@ -162,16 +162,17 @@ export class ChromeConnection {
/**
* Attach the websocket to the first available tab in the chrome instance with the given remote debugging port number.
*/
public attach(port: number, url?: string): Promise<void> {
public attach(port: number, url?: string, address?: string): Promise<void> {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Logically I'd expect tha arguments to be : Address, port and url.

This smells of an after-thought... just one more param, right? I'd rather make sure the arguments are ordered logically, bump the sem-major version and update the two consumers of this debugger (edge + chrome)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought about it. But since port is required, the other two are optional.
Having port, address, url looks equally weird as well.

On Tuesday, June 21, 2016, Kenneth Auchenberg notifications@github.com
wrote:

In src/chrome/chromeConnection.ts
#50 (comment)
:

@@ -162,16 +162,17 @@ export class ChromeConnection {
/**
* Attach the websocket to the first available tab in the chrome instance with the given remote debugging port number.
*/

  • public attach(port: number, url?: string): Promise {
  • public attach(port: number, url?: string, address?: string): Promise {

Logically I'd expect tha arguments to be : Address, port and url.

This smells of an after-thought... just one more param, right? I'd rather
make sure the arguments are ordered logically, bump the sem-major version
and update the two consumers of this debugger (edge + chrome)


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode-chrome-debug-core/pull/50/files/813face911502dab6c1b5d5bb3b3c8f2e2a7b9c9#r67997645,
or mute the thread
https://github.com/notifications/unsubscribe/AA-JVFpWtl7_wmkZg5pp2ywh03JzgMlGks5qOMzrgaJpZM4I7Oc5
.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point!

roblourens added a commit that referenced this pull request Jul 20, 2016
Not using browser-launcher2 because it forces a bunch of CLI params that I don't want. Not using a package to detect browsers because this is straightforward. And not moving launching out of -core because it's used by the cordova extension which consumes -core, and makes sense to keep it.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants