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

jest-haste-map: add test case for broken handling of ignore pattern #4047

Merged
merged 1 commit into from
Jul 17, 2017

Conversation

jeanlauliac
Copy link
Contributor

This adds a test to keep track of the broken behavior for when ignorePattern is changed. Normally, the new ignore pattern should be applied, that means new files may now have to be included, and that others may now have to be ignored. However this is not properly handled at the moment, the ignorePattern is ignored when there's already a cache.

By adding this test now, we can simply switch the "expect" line when this is fixed.

Test plan

yarn run jest packages/jest-haste-map/src/__tests__/index.test.js

@jeanlauliac jeanlauliac requested a review from cpojer July 17, 2017 15:40
@cpojer cpojer merged commit c2bf42c into jestjs:master Jul 17, 2017
facebook-github-bot pushed a commit to facebook/metro that referenced this pull request Jul 17, 2017
Summary: I'd like to get rid of the function as blacklist, because it's impossible to process properly at the `jest-haste-map` level (jestjs/jest#4047). The reason we use a function in Metro bundler is because we excludes all the `__tests__` modules. However, I removed this exclusion completely, and I could build our package without any problem and with no difference in the final bundle. I can only assume, then, that this line is only here for slightly increasing performance. Therefore, I think it's reasonnable to move it as part of the default blacklist shipped with Metro bundler instead.

Reviewed By: cpojer

Differential Revision: D5434351

fbshipit-source-id: dea39f6299985143d25fcb3b7b365d793acd64a9
@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 May 13, 2021
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