-
Notifications
You must be signed in to change notification settings - Fork 63
Remove .ts from binary extensions to fix TypeScript file processing
#236
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -51,8 +51,11 @@ pub const BINARY_FILE_EXTENSIONS: &[&str] = &[ | |
| "wma", "ra", "ram", "ape", "opus", "amr", "awb", | ||
|
|
||
| // Video | ||
| // Note: .ts (MPEG transport stream) extension is intentionally excluded | ||
| // to avoid conflicts with TypeScript files, which are more common in code repositories. | ||
| // Actual binary .ts files will still be detected via content inspection. | ||
| "mp4", "m4v", "mov", "avi", "wmv", "mkv", "flv", "f4v", "f4p", "f4a", "f4b", "3gp", | ||
| "3g2", "mpeg", "mpg", "mpe", "m1v", "m2v", "ts", "mts", "m2ts", "vob", "rm", "rmvb", | ||
|
Owner
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @copilot
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Correct - the content inspection in |
||
| "3g2", "mpeg", "mpg", "mpe", "m1v", "m2v", "mts", "m2ts", "vob", "rm", "rmvb", | ||
| "asf", "ogv", "ogm", "webm", "dv", "divx", "xvid", | ||
|
|
||
| // Font Files | ||
|
|
||
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.
The multi-line comment should follow Rust's convention of using
//for each line rather than placing it as a separate block before the array line. This would be more consistent with the single-line comments used elsewhere in this file (e.g., line 10, 11, 18, etc.).