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(deps): bump rimraf from 2.6.2 to 5.0.10 #358

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

mrkans
Copy link

@mrkans mrkans commented Sep 19, 2024

Description

Fixes #355

Motivation and Context

How Has This Been Tested?

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation (adding or updating documentation)
  • Dependency update

Checklist:

  • My change requires a change to the documentation and I have updated the documentation accordingly.
  • My changes are in sync with the code style of this project.
  • There aren't any other open Pull Requests for the same issue/update.
  • These changes should be applied to a maintenance branch.
  • I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using Jest-Image-Snapshot?

@mrkans mrkans requested a review from a team as a code owner September 19, 2024 07:57
@CLAassistant
Copy link

CLAassistant commented Sep 19, 2024

CLA assistant check
All committers have signed the CLA.

@@ -271,10 +271,10 @@ function diffImageToSnapshot(options) {
result = { added: true };
} else {
const receivedSnapshotPath = path.join(receivedDir, `${snapshotIdentifier}${receivedPostfix}.png`);
rimraf.sync(receivedSnapshotPath);
rimrafSync(receivedSnapshotPath, { glob: true });
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is glob: true required here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test cases pass without glob: true here.
Without it in integration.spec.js an error is thrown stating "Illegal characters in path.".
Since the path came from options then I´m not sure if it can become a problem without setting glob to true so I added it here as well. If you think this assumption is wrong then I have no problem removing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

update rimraf dependency
3 participants