-
Notifications
You must be signed in to change notification settings - Fork 99
Add launch.json to the project #1581
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
base: main
Are you sure you want to change the base?
Conversation
PR Summary
|
|
Hello. You need to create a changeset file and commit it to let this change be approved. Could you run ERROR: The following projects have been changed and require change descriptions,
but change descriptions were not detected for them:
- @boostercloud/framework-core
To resolve this error, run "rush change". This will generate change description
files that must be committed to source control. |
|
@davidverdu Now it's fine sir, I have generated the changeset and its seems to fine. |
|
/integration sha=6126df160824fe5d0b7bfebb7a66205c51989f4b |
|
⌛ Integration tests are running... Check their status here 👈 |
|
✅ Integration tests have finished successfully! |
|
@davidverdu sir , Can u check it out as if it's ok to merge. |
Description
This PR adds automatic generation of a
.vscode/launch.jsonfile when creating new Booster projects. This provides developers with a pre-configured VS Code debug setup for running unit tests, improving the development experience.Changes
launch-json.tstemplate - Created a new template file with VS Code launch configuration for unit testsproject-initializer.tsto:.vscodedirectory during project initialization.vscode/launch.jsonfile with the template content.vscodedirectory creation ingenerateRootDirectory()function.vscode/launch.jsonfile generation ingenerateConfigFiles()functionChecks
Additional information
This enhancement improves the developer experience by automatically providing a VS Code debug configuration when creating new Booster projects. The generated
.vscode/launch.jsonfile includes:rushx test${workspaceFolder})The implementation follows the existing codebase patterns and maintains backward compatibility. All existing functionality continues to work as expected, and the new feature is thoroughly tested.