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

Investigate using VS Code debugger on samples #10334

Closed
deyaaeldeen opened this issue Jul 29, 2020 · 1 comment · Fixed by #13960
Closed

Investigate using VS Code debugger on samples #10334

deyaaeldeen opened this issue Jul 29, 2020 · 1 comment · Fixed by #13960
Assignees
Labels
Client This issue points to a problem in the data-plane of the library.
Milestone

Comments

@deyaaeldeen
Copy link
Member

dev-tools compiles samples and runs them from a different location making them hard to debug.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jul 29, 2020
@deyaaeldeen deyaaeldeen self-assigned this Jul 29, 2020
@deyaaeldeen deyaaeldeen added this to the Backlog milestone Jul 29, 2020
@deyaaeldeen deyaaeldeen removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jul 29, 2020
@ramya-rao-a ramya-rao-a added the Client This issue points to a problem in the data-plane of the library. label Jul 30, 2020
@deyaaeldeen
Copy link
Member Author

The VS Code debugger can be used on the compiled js files located in dist-samples/typescript/dist/dist-samples/typescript/src/ with the following profile:

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Current JS file",
            "program": "${file}",
            "outFiles": [
                "${workspaceFolder}/dist-esm/**/*.js"
            ],
            "envFile": "${workspaceFolder}/.env"
        }
    ]
}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants