Skip to content
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

Test "serverReadyAction" feature #69313

Closed
2 tasks done
weinand opened this issue Feb 24, 2019 · 0 comments
Closed
2 tasks done

Test "serverReadyAction" feature #69313

weinand opened this issue Feb 24, 2019 · 0 comments
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues testplan-item
Milestone

Comments

@weinand
Copy link
Contributor

weinand commented Feb 24, 2019

Test for #69311:

Complexity: 3

Authors: @weinand

For a description of the feature, please see #69311 (comment).

Verify....

  • you can use Intellisense to add the serverReadyAction property (and its properties) to any launch config and hovering over the properties explains what they do.
  • it works out of the box for a node.js "express" application both for openExternally and debugWithChrome actions (see https://code.visualstudio.com/docs/nodejs/nodejs-tutorial#_an-express-application for how to create an express app)
  • create a simple server application in another language (e.g. C# or Python, etc.) and configure the pattern property to match the trigger message.
  • modify the urlFormat to make VS Code use a "https" URI (for a port pattern).

Please note:
There is an inconsistency with the property "uriFromat": Intellisense suggests "uriFormat" but the code actually expects "urlFormat". So you will have to use "urlFormat" until this is fixed (#69344).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues testplan-item
Projects
None yet
Development

No branches or pull requests

3 participants