chore: add VsCode debug config with clean cache #17229
Merged
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.
Changes
This PR adds an additional debug config, which executes the
clean-cache
command to clean the cache before running.Context
When debugging datasources it is quite important to have a clean cache to verify if things are working. I noticed that while manually executing
clean-cache
beforehand solves that, this PR packages it in a handy launch command, which you can directly execute from the VsCode debug console. It copies thelaunch
command completely and just adds apreLaunchTask
to clean the cache.The task
npm: clean-cache
is a vscode notion for automatically created tasks based on the commands from thepackage.json
. It does actually executeyarn run clean-cache
underneath:Based on the discussion in https://renovatebot.slack.com/archives/CAFH752JU/p1660038460461659
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via:
Tested in my local development setup without any negative impacts.