8000 [turbopack] Delete the `read_glob` function (#79166) · vercel/next.js@5d73b2f · GitHub
[go: up one dir, main page]
Skip to content

Commit 5d73b2f

Browse files
lukesandberglukesandberg
authored
[turbopack] Delete the read_glob function (#79166)
Why? This was only used for unit tests and an example. Also, the API was a little strange, it would end up creating a `Vc` that depended on all the directories with matches and produced a value that modeled the matching directory tree. Happy to replace the example... I wasn't really sure what those were used for.
1 parent 15942fc commit 5d73b2f

File tree

3 files changed

+50
-361
lines changed

3 files changed

+50
-361
lines changed

‎turbopack/crates/turbo-tasks-fs/examples/hash_glob.rs

Lines changed: 0 additions & 120 deletions
This file was deleted.

‎turbopack/crates/turbo-tasks-fs/src/lib.rs

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -46,8 +46,7 @@ use invalidator_map::InvalidatorMap;
4646
use jsonc_parser::{ParseOptions, parse_to_serde_value};
4747
use mime::Mime;
4848
use rayon::iter::{IntoParallelIterator, ParallelIterator};
49-
pub use read_glob::ReadGlobResult;
50-
use read_glob::{read_glob, track_glob};
49+
use read_glob::track_glob;
5150
use rustc_hash::FxHashSet;
5251
use serde::{Deserialize, Serialize};
5352
use serde_json::Value;
@@ -1263,15 +1262,6 @@ impl FileSystemPath {
12631262
Ok(FileSystemPathOption::none())
12641263
}
12651264

1266-
#[turbo_tasks::function]
1267-
pub fn read_glob(
1268-
self: Vc<Self>,
1269-
glob: Vc<Glob>,
1270-
include_dot_files: bool,
1271-
) -> Vc<ReadGlobResult> {
1272-
read_glob(self, glob, include_dot_files)
1273-
}
1274-
12751265
// Tracks all files and directories matching the glob
12761266
// Follows symlinks as though they were part of the original hierarchy.
12771267
#[turbo_tasks::function]

0 commit comments

Comments
 (0)
0