From 25dedc1c367f9c9a84e94fdb281ae39073c0baf2 Mon Sep 17 00:00:00 2001 From: Renamr Scaffold Date: Sun, 30 Aug 2026 04:41:43 +0000 Subject: [PATCH] Remove remaining user-visible FileBot mentions The full rebrand (session 9, seventh delivery) covered the app's own identity - name, icon, no FileBot/FB-Mod branding visible - but two literal "FileBot" mentions were still reachable by the end user, both found via a targeted grep for FileBot/Filebot/filebot/FB-Mod across every string actually rendered to a user (JSX text and CLI help/usage text), as opposed to source comments and README documentation, which still legitimately explain what this project is a rewrite of and aren't shown inside the running app: - The Naming Scheme editor's own inline help text described the FileBot- style short field names ({n}, {s00e00}, {t}, etc.) as "FileBot's own short field names" - reworded to just "Short field names", same meaning, no brand name. - The CLI's -h/--help output described -non-strict as "Accepted for FileBot script compatibility" - reworded to "Accepted for compatibility with existing rename scripts". Grepped the whole frontend and every Rust source string (not just these two files) to confirm nothing else user-visible remained - tauri.conf.json, Cargo.toml, and package.json were already clean. What's left after this is exclusively source-code comments/doc-comments and README.md, none of which the app itself ever displays. Verified via cargo test --workspace (193/193, unaffected - text-only change) + npm run build (clean). --- src-tauri/src/cli.rs | 5 +++-- src/components/RenamePanel.tsx | 8 ++++---- 2 files changed, 7 insertions(+), 6 deletions(-) diff --git a/src-tauri/src/cli.rs b/src-tauri/src/cli.rs index 6d9c057..bc719ee 100644 --- a/src-tauri/src/cli.rs +++ b/src-tauri/src/cli.rs @@ -46,8 +46,9 @@ Options: movies are also looked up online when this is tmdb or omdb - TVmaze has no movie catalog) --action What to do with each file (default: move; \"test\" prints the plan without touching anything) --conflict What to do when a computed target already exists (default: skip) - -non-strict Accepted for FileBot script compatibility; has no effect (local matching has no - confidence score to loosen - see the aurora_curator_core::cli module doc) + -non-strict Accepted for compatibility with existing rename scripts; has no effect (local + matching has no confidence score to loosen - see the aurora_curator_core::cli + module doc) -h, --help Show this help and exit A --db tmdb/omdb source needs the matching API token/key already saved through the app's own Fetch Data diff --git a/src/components/RenamePanel.tsx b/src/components/RenamePanel.tsx index 0d5277c..77df744 100644 --- a/src/components/RenamePanel.tsx +++ b/src/components/RenamePanel.tsx @@ -1695,10 +1695,10 @@ export default function RenamePanel() { need their own free API credential set there first). The separate Fetch Data button next to New Names still works on its own too, for re-fetching after changing the source or fixing a guessed name by hand. A batch can freely mix TV and movie files, even against different sources — each file only fills in the - fields that apply to it. FileBot's own short - field names ({"{n}"}, {"{s00e00}"}, {"{t}"}, {"{y}"}, - {"{vf}"}, {"{vc}"}, {"{ac}"}, {"{group}"}, etc.) still - work too, side by side with the names above. + fields that apply to it. Short field names ({"{n}"}, {"{s00e00}"},{" "} + {"{t}"}, {"{y}"}, {"{vf}"}, {"{vc}"},{" "} + {"{ac}"}, {"{group}"}, etc.) still work too, side by side with the names + above.

Use {"/"} in the scheme to organize files into subfolders as part of renaming, e.g.{" "}