Performance tuning for getProjectFiles #612
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relate #610
In
getProjectFiles
, the process of checking for file name conflicts is very heavy.However, this process was placed before filtering files using ignore.
That is, this process was applied to a large number of files (for example, files in
node_modules
), and spend long time.Therefore, Ie speeded up by replacing the processing order.
The process of checking for file name conflicts is running before filtering words by ignore.
npm run test
succeeds.npm run lint
succeeds.