-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: collapse generated snapshots in PR view by default #6485
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: collapse generated snapshots in PR view by default #6485
Conversation
Thanks for the PR, @Josh-Cena! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #6485 +/- ##
==========================================
+ Coverage 90.64% 90.66% +0.02%
==========================================
Files 373 374 +1
Lines 12751 12823 +72
Branches 3752 3777 +25
==========================================
+ Hits 11558 11626 +68
Misses 853 853
- Partials 340 344 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Won't this remove the syntax highlighting in GH because you're losing the language attribute? I don't know if they should be seen as generated - aside from codebase reactors, we'll really want to be reviewing all of our snapshots as code because they represent the AST output. I do have an idea for adding snapshot testing to the rule tester as well, so that would be more snapshots to be reviewed. |
No it won't.
You can still view the diff, just that they are collapsed by default. This prevents diffs like #6274 from being unviewable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as syntax highlighting is preserved, I'm fine with auto-collapsing by default. I normally end up doing little console macros to collapse/expand everything anyway.
PR Checklist
Overview
Per discussion with @JoshuaKGoldberg. This makes snapshots collapsed just like
yarn.lock
changes.