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: ensure all exported files have a consistent filename #12329

Merged
merged 1 commit into from
Feb 9, 2022

Conversation

SimenB
Copy link
Member

@SimenB SimenB commented Feb 8, 2022

Summary

This makes the tooling for bundling a bit cleaner. Also, consistency is always good to reduce any extra mental overhead..

This is not breaking since we do not support deep access of our modules, but I'll stick it in Jest 28 anyways just to be a bit nice to people doing illegal stuff

Test plan

Green CI

@codecov-commenter
Copy link

Codecov Report

Merging #12329 (a40c5dc) into main (55caeb7) will decrease coverage by 0.00%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #12329      +/-   ##
==========================================
- Coverage   67.26%   67.26%   -0.01%     
==========================================
  Files         330      330              
  Lines       17352    17352              
  Branches     5071     5071              
==========================================
- Hits        11672    11671       -1     
- Misses       5648     5649       +1     
  Partials       32       32              
Impacted Files Coverage Δ
packages/expect/src/utils.ts 96.09% <0.00%> (-0.49%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 55caeb7...a40c5dc. Read the comment docs.

@SimenB SimenB merged commit f6c809b into jestjs:main Feb 9, 2022
@SimenB SimenB deleted the consistent-filename branch February 9, 2022 10:47
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

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

Successfully merging this pull request may close these issues.

3 participants