-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Make ignorePattern optional in HasteMap #7166
Make ignorePattern optional in HasteMap #7166
Conversation
73adb54
to
03199e5
Compare
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.
LGTM 👍
03199e5
to
c3bef12
Compare
@@ -54,7 +54,7 @@ type Options = { | |||
extensions: Array<string>, | |||
forceNodeFilesystemAPI?: boolean, | |||
hasteImplModulePath?: string, | |||
ignorePattern: HasteRegExp, | |||
ignorePattern?: ?HasteRegExp, |
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.
Both?
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.
It was just convenient to avoid handling optional properties in the options passed from jest-runtime
. Options
has it as an optional nullable property and InternalOptions
has it only nullable (not optional). Not sure if this is considered a bad practice though.
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. |
Summary
This removes the need to pass an ignore pattern to new instances of
HasteMap
and updatesjest-runtime
so it doesn't pass one unless it's necessary.Test plan
Updated the current tests and tested in FB infra.