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

There is no a dependency named "dependsOn" for Express.js application #48

Closed
v-dantch opened this issue Mar 2, 2020 · 2 comments
Closed
Labels
AT-CTI Issues found by internal test team

Comments

@v-dantch
Copy link

v-dantch commented Mar 2, 2020

OS: Windows
Build Version: 20200228.2
Node.js Version: 12.x.x
image

Repro Steps:

  1. Create and initialize a new Express.js application by below:

npx express-generator nodeapp
cd nodeapp
npm install

  1. Open this application folder in VS Code --> Switch to the debug tab -->Select "create a launch.json" file --> Select "Node.js" when asked to select an environment.
  2. Select "Dapr: Scaffold Dapr Tasks" from Command Palette --> Select "Launch Program" when asked to select a configuration --> Enter an application ID --> Enter an application port.
  3. Open the ".vscode/tasks.json" file --> Check whether there is a dependency ("dependsOn") and it should set to "build".

Expect:
There is a dependency ("dependsOn") and it has been set to "build".

Actual:
There is no a dependency named "dependsOn".
image

@philliphoff philliphoff added the AT-CTI Issues found by internal test team label Mar 2, 2020
@philliphoff
Copy link
Collaborator

@v-dantch You're right, that's a test case bug. The task in the Node.js scenario should not have a "dependsOn" property as there's no build step for that kind of Node.js application (as the JavaScript is interpreted and not compiled). I've updated the test case.

@v-dantch
Copy link
Author

v-dantch commented Mar 3, 2020

Hi @philliphoff , thanks a lot for your share and help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AT-CTI Issues found by internal test team
Projects
None yet
Development

No branches or pull requests

2 participants