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

chore: add VsCode debug config with clean cache #17229

Merged
merged 1 commit into from Aug 17, 2022

Conversation

Shegox
Copy link
Contributor

@Shegox Shegox commented Aug 17, 2022

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 the launch command completely and just adds a preLaunchTask to clean the cache.

The task npm: clean-cache is a vscode notion for automatically created tasks based on the commands from the package.json. It does actually execute yarn run clean-cache underneath:
image

Based on the discussion in https://renovatebot.slack.com/archives/CAFH752JU/p1660038460461659

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

Tested in my local development setup without any negative impacts.

@viceice viceice merged commit 768e06c into renovatebot:main Aug 17, 2022
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 32.162.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants