Refactor VSCode tasks and launch configurations for improved build and test processes #123
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request updates the VS Code configuration to streamline build and test workflows and remove unused PowerShell launch configurations. The main focus is shifting build and test automation to use
Invoke-Buildtasks, improving consistency and maintainability.Build and Test Workflow Improvements:
.vscode/tasks.jsonwith standardizedInvoke-Buildtasks forBootstrap,Clean Build, andBuildoperations, simplifying the build process and making it easier to maintain.Test,UnitTests,IntegrationTests,PSScriptAnalyzer,InjectionHunter, andExport-CommandHelpin.vscode/tasks.json, enabling easier execution of common development and QA tasks directly from VS Code.Configuration Cleanup:
.vscode/launch.jsonthat are no longer needed, reducing clutter and potential confusion for developers.Type of Change