Skip to content

fix(no-large-snapshots): use a far better message for when an unexpected snapshot is found #1736

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

Merged
merged 2 commits into from
May 25, 2025

Conversation

ulrichstark
Copy link
Contributor

The incorrect message was introduced by #278

@ulrichstark ulrichstark changed the title fix(no-large-snapshosts): fix incorrect noSnapshot message fix(no-large-snapshots): fix incorrect noSnapshot message May 25, 2025
@G-Rath G-Rath changed the title fix(no-large-snapshots): fix incorrect noSnapshot message fix(no-large-snapshots): use a far better message for when an unexpected snapshot is found May 25, 2025
Copy link
Collaborator

@G-Rath G-Rath left a comment

Choose a reason for hiding this comment

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

wow, I can't believe that has been around for so long 😅

@G-Rath G-Rath added this pull request to the merge queue May 25, 2025
Merged via the queue into jest-community:main with commit 0f5b873 May 25, 2025
51 checks passed
@ulrichstark ulrichstark deleted the fix-wrong-message branch May 25, 2025 19:22
camc314 pushed a commit to oxc-project/oxc that referenced this pull request May 25, 2025
- re-word diagnostic messages ("Disallow large snapshots." => "Snapshot
is too long.")
- fix incorrect help message
- related:
jest-community/eslint-plugin-jest#1736
- add test to include `no_snapshot` diagnostic in test snapshot
- minor other code refactorings to improve readability
@G-Rath
Copy link
Collaborator

G-Rath commented May 25, 2025

@SimenB this failed release due to the merge queue requirement:

[7:17:27 PM] [semantic-release] › ✘  An error occurred while running semantic-release: Error: Command failed with exit code 1: git push --tags https://x-access-token:[secure]@github.com/jest-community/eslint-plugin-jest.git HEAD:main
remote: error: GH006: Protected branch update failed for refs/heads/main.        
remote: 
remote: - Changes must be made through the merge queue        
remote: 
remote: - 43 of 43 required status checks are expected.  

fwiw, I'm not super worried about renovate merging PRs with a failing CI as that doesn't happen a whole lot, so feel free to just disable the merge queue for now

github-actions bot pushed a commit that referenced this pull request May 27, 2025
## [28.11.1](v28.11.0...v28.11.1) (2025-05-27)

### Bug Fixes

* **no-large-snapshots:** use a far better message for when an unexpected snapshot is found ([#1736](#1736)) ([0f5b873](0f5b873))
Copy link

🎉 This PR is included in version 28.11.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

2 participants