feat(web): add path autocomplete to set location dialog

[nitrobass24]

Summary

• Wires up the existing usePathAutocomplete hook in the SetLocationDialog so that existing torrents get the same directory autocomplete dropdown available when adding new torrents
• Adds a handleBlur callback to usePathAutocomplete to dismiss the dropdown when clicking outside the input
• Updates all three call sites (TorrentTableOptimized, TorrentManagementBar, TorrentCardsMobile) to pass instanceId and capabilities to SetLocationDialog

Note: This PR depends on PR #1431 which adds the trailing slash auto-append behavior to usePathAutocomplete. That PR should be merged first.

Fixes #857

Test plan

• Select one or more existing torrents and open the "Set Location" dialog
• Type a path and verify the autocomplete dropdown appears with directory suggestions
• Select a directory and verify / is appended and subdirectories load
• Click outside the input and verify the dropdown dismisses
• Press Escape and verify the dropdown dismisses
• Verify keyboard navigation (Arrow keys, Enter, Tab) works in the dropdown
• Verify the "Set Location" button submits the selected path correctly
• Verify autocomplete works from the management bar, context menu, and mobile card views

Summary by CodeRabbit

• New Features

  • Path autocomplete in location dialogs with inline, clickable directory suggestions and continued navigation into subfolders.
  • Location dialog provides contextual, instance-aware suggestions for more relevant results.

• Bug Fixes / Behavior

  • Selecting a suggestion appends a trailing slash and keeps focus for further navigation.
  • Losing focus cleanly dismisses suggestions; keyboard interactions route through autocomplete for expected behavior.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

Walkthrough

SetLocationDialog is extended with optional instanceId and capabilities props and wired to usePathAutocomplete; callers in several torrent UI components now pass these props. Autocomplete state, selection, and blur handling are integrated into the dialog.

Changes

Cohort / File(s)	Summary
SetLocationDialog (autocomplete integration) web/src/components/torrents/TorrentDialogs.tsx	Adds optional instanceId?: number and `capabilities?: InstanceCapabilities
Prop propagation to callers web/src/components/torrents/TorrentCardsMobile.tsx, web/src/components/torrents/TorrentManagementBar.tsx, web/src/components/torrents/TorrentTableOptimized.tsx	Passes instanceId and capabilities through to SetLocationDialog invocations so the dialog can enable instance-aware path autocomplete.
Autocomplete hook update web/src/hooks/usePathAutocomplete.ts	Modifies selectSuggestion to append trailing slash and keep dropdown open for subdirectory navigation, exposes handleBlur to dismiss dropdown on input blur, and tweaks focus behavior after selection.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant SetLocationDialog
    participant usePathAutocomplete
    participant FilesystemAPI

    User->>SetLocationDialog: open (includes instanceId, capabilities)
    SetLocationDialog->>usePathAutocomplete: init/sync(instanceId, capabilities)
    usePathAutocomplete->>FilesystemAPI: request suggestions for path
    FilesystemAPI-->>usePathAutocomplete: return suggestions
    usePathAutocomplete-->>SetLocationDialog: provide suggestions
    SetLocationDialog-->>User: render suggestions dropdown
    User->>SetLocationDialog: type / arrow / click suggestion
    SetLocationDialog->>usePathAutocomplete: handleAutocompleteChange / handleSelect / handleAutocompleteKeyDown
    usePathAutocomplete->>FilesystemAPI: fetch deeper suggestions (if needed)
    FilesystemAPI-->>usePathAutocomplete: return updated suggestions
    usePathAutocomplete-->>SetLocationDialog: update suggestions (keeps open)
    User->>SetLocationDialog: blur input
    SetLocationDialog->>usePathAutocomplete: handleBlur -> dismiss suggestions

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• refactor(web): use TanStack Query for path autocomplete #1309: Refactors/enhances usePathAutocomplete and related directory content logic used by this change.
• fix(web): auto-append slash on path autocomplete selection #1431: Adjusts selection behavior (trailing slash, dropdown focus/dismissal) in the autocomplete hook.
• feat(torrents): autocomplete paths #634: Prior work introducing path-autocomplete integration and wiring into SetLocationDialog.

Suggested labels

enhancement, web, torrent

Suggested reviewers

• s0up4200

Poem

🐇 I hop through folders, nudging paths to show,

I add a slash and let the suggestions flow.
Dropdown stays open, I guide each little click,
Type, select, or blur — I'll help you pick.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding path autocomplete functionality to the set location dialog for existing torrents.
Linked Issues check	✅ Passed	All code requirements from issue #857 are met: path autocomplete integrated into SetLocationDialog, reusing usePathAutocomplete hook, and propagated across all call sites.
Out of Scope Changes check	✅ Passed	All changes directly support the stated objective of enabling autocomplete for existing torrent location dialogs; no unrelated modifications detected.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@web/src/components/torrents/TorrentDialogs.tsx`:
- Around line 628-636: In handleKeyDown, prevent submitting when the
autocomplete handler already handled the Enter key: after calling
handleAutocompleteKeyDown (when supportsPathAutocomplete is true), check
e.defaultPrevented (or e.defaultPrevented === true) before running the
Enter-to-submit branch; if default is prevented, do not call handleConfirm.
Update the logic in the handleKeyDown callback (which references
supportsPathAutocomplete, handleAutocompleteKeyDown, location, isPending, and
handleConfirm) so Enter presses consumed by autocomplete won't fall through and
submit the stale location.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@web/src/components/torrents/TorrentDialogs.tsx`:
- Around line 668-692: The dropdown uses a non-existent Tailwind class
"max-h-55" which is dropped by the CSS build; replace "max-h-55" with a valid
utility like "max-h-56" or an arbitrary value "max-h-[13.75rem]" in the
component rendering the suggestions (look for the div containing "max-h-55
overflow-y-auto py-1" inside TorrentDialogs's suggestions map and update the
class there), and apply the same fix for the two other occurrences in
TorrentCreatorDialog.tsx and AddTorrentDialog.tsx.

🧹 Nitpick comments (1)

web/src/components/torrents/TorrentDialogs.tsx (1)

604-614: effectiveInputRef in the dependency array is a ref object — harmless but unnecessary.

Ref objects have a stable identity across renders, so including effectiveInputRef in the dep array won't cause re-runs but adds noise. Not a blocking issue.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

echo "=== Checking Tailwind version ==="
if [ -f "package.json" ]; then
  cat package.json | grep -A 2 -B 2 "tailwind" || echo "No tailwind found in package.json"
fi

echo -e "\n=== Checking for Tailwind config files ==="
fd "tailwind.config" --type f

echo -e "\n=== Checking TailwindCSS content in project ==="
find . -maxdepth 3 -name "tailwind.config.*" -type f -exec cat {} \;

echo -e "\n=== Searching for max-h-55 usage ==="
rg "max-h-55" --type tsx --type ts --type jsx --type js -n

echo -e "\n=== Checking standard Tailwind spacing scale documentation ==="
rg "max-h-5[0-9]" --type tsx --type ts -n | head -20

Repository: autobrr/qui

Length of output: 356

---

🏁 Script executed:

#!/bin/bash

echo "=== Checking package.json for Tailwind ==="
cat package.json | grep -i "tail\|css"

echo -e "\n=== Searching for max-h-55 without file type filter ==="
rg "max-h-55" 2>/dev/null || echo "max-h-55 not found"

echo -e "\n=== Looking for TorrentDialogs.tsx ==="
fd "TorrentDialogs.tsx" --type f

echo -e "\n=== Checking lines around 671 in TorrentDialogs.tsx ==="
fd "TorrentDialogs.tsx" --type f -exec sed -n '665,675p' {} \;

echo -e "\n=== Searching for tailwind config ==="
find . -name "tailwind*" -o -name "postcss*" | grep -v node_modules | head -10

echo -e "\n=== Checking for any max-h- classes ==="
rg "max-h-" 2>/dev/null | head -20

Repository: autobrr/qui

Length of output: 4089

---

🏁 Script executed:

#!/bin/bash

echo "=== Checking postcss.config.js ==="
cat ./documentation/postcss.config.js

echo -e "\n=== Looking for globals or CSS files that might define max-h-55 ==="
fd "\.(css|scss)$" --type f | head -20

echo -e "\n=== Checking if there's a tailwind.config in root or app directories ==="
find . -maxdepth 2 -type f \( -name "tailwind.config.*" -o -name "vite.config.*" \)

echo -e "\n=== Checking what build tool is used ==="
ls -la | grep -E "vite|webpack|next"

echo -e "\n=== Looking for CSS files in src ==="
find ./web/src -name "*.css" | head -20

Repository: autobrr/qui

Length of output: 1015

---

🏁 Script executed:

#!/bin/bash

echo "=== Checking Tailwind version in lock files ==="
grep -i "tailwind\|@tailwindcss" package-lock.json 2>/dev/null | head -10 || echo "No package-lock.json"
grep -i "tailwind\|@tailwindcss" pnpm-lock.yaml 2>/dev/null | head -10 || echo "No pnpm-lock.yaml"
grep -i "tailwind\|@tailwindcss" yarn.lock 2>/dev/null | head -10 || echo "No yarn.lock"

echo -e "\n=== Checking web directory structure ==="
ls -la web/ | grep -E "package|tsconfig|tailwind"

echo -e "\n=== Checking web/package.json for dependencies ==="
cat web/package.json 2>/dev/null | grep -A 20 '"dependencies"' | grep -i "tailwind\|css"

echo -e "\n=== Checking web/package.json full ==="
cat web/package.json 2>/dev/null | head -50

echo -e "\n=== Checking for any tailwind config in web/ ==="
find ./web -maxdepth 2 -type f \( -name "tailwind.config.*" -o -name ".tw*" \)

echo -e "\n=== Checking web/src/index.css for Tailwind imports ==="
head -20 web/src/index.css

Repository: autobrr/qui

Length of output: 3138

---

🏁 Script executed:

#!/bin/bash

echo "=== Checking for Tailwind package in dependencies ==="
cat web/package.json | grep -E "@tailwindcss|tailwindcss"

echo -e "\n=== Checking root package.json if exists ==="
if [ -f "package.json" ]; then
  cat package.json | head -100
fi

echo -e "\n=== Checking pnpm-lock.yaml or yarn.lock for Tailwind version ==="
if [ -f "pnpm-lock.yaml" ]; then
  grep -A 5 "@tailwindcss/postcss" pnpm-lock.yaml | head -20
elif [ -f "yarn.lock" ]; then
  grep -A 5 "@tailwindcss/postcss" yarn.lock | head -20
fi

echo -e "\n=== Checking if max-h-55 is actually rendered/used in styles ==="
# Check if there's any CSS preprocessing that might handle max-h-55
rg "55|max-height.*55" web/src/themes/ | head -10

echo -e "\n=== Looking at Tailwind v4 arbitrary value documentation - checking if max-h-55 works ==="
# Let's check if there's any indication in comments or docs about Tailwind v4
rg -i "tailwind.*v4|arbitrary" web/ | head -10

Repository: autobrr/qui

Length of output: 1206

---

🏁 Script executed:

#!/bin/bash

echo "=== Checking Tailwind v4 spacing scale and max-h utilities ==="
# In Tailwind v4, check what max-h utilities would be generated
# Standard scale: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 14, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64, 80, 96
# max-h-55 is not in this standard scale
echo "Standard Tailwind spacing scale does NOT include 55"
echo "It goes: ..., max-h-52 (13rem), max-h-56 (14rem), ..."
echo "max-h-55 would be 13.75rem"

echo -e "\n=== Checking if there's any custom Tailwind configuration ==="
find ./web -type f -name "tailwind.config.*" -o -name "tailwind.json"

echo -e "\n=== Checking vite.config for Tailwind plugin config ==="
cat ./web/vite.config.ts | head -50

echo -e "\n=== Checking if max-h-55 is defined in any CSS file ==="
rg "max-h-55" web/src/ --type css || echo "Not found in CSS files"

echo -e "\n=== Verifying the actual line in TorrentDialogs.tsx ==="
sed -n '668,675p' web/src/components/torrents/TorrentDialogs.tsx

Repository: autobrr/qui

Length of output: 2992

---

🏁 Script executed:

#!/bin/bash

echo "=== Testing if Tailwind v4 auto-arbitrary would handle max-h-55 ==="
# In Tailwind v4, arbitrary values require bracket notation
# max-h-55 as a plain utility class is NOT automatically generated
# It would need to be: max-h-[13.75rem]

echo "Tailwind v4 automatic value support requires bracket notation like max-h-[13.75rem]"
echo "Plain max-h-55 without a matching spacing scale entry will NOT work"

echo -e "\n=== Checking what happens with max-h classes in practice ==="
rg "max-h-\[" web/src/ --type tsx | head -5
rg "max-h-[0-9]+" web/src/ --type tsx | grep -v "max-h-\[" | head -10

Repository: autobrr/qui

Length of output: 409

---

🏁 Script executed:

#!/bin/bash

echo "=== Checking max-h usage patterns ==="
rg "max-h-" web/src/components/torrents/ | head -20

echo -e "\n=== Verifying what max-h utilities exist in standard Tailwind ==="
# Check the actual behavior - list all max-h uses
rg "max-h-" web/src/ | grep -E "max-h-[0-9]+" | cut -d: -f2 | sort | uniq

echo -e "\n=== Double checking: are there any custom height definitions? ==="
rg "heights|spacing" web/ --type json || echo "No custom heights config found"

Repository: autobrr/qui

Length of output: 5111

---

max-h-55 is not a valid Tailwind utility and will be silently ignored.

Line 671 uses max-h-55, which is not in Tailwind's default spacing scale (which includes max-h-52 and max-h-56 but skips 53-55). In Tailwind v4.1.17 with no custom height config, this class will be dropped during CSS generation, leaving the dropdown without a height constraint.

Use max-h-56 (14rem) or the arbitrary value max-h-[13.75rem] for the intended height. This issue also appears in TorrentCreatorDialog.tsx and AddTorrentDialog.tsx (2 instances).

🤖 Prompt for AI Agents

In `@web/src/components/torrents/TorrentDialogs.tsx` around lines 668 - 692, The
dropdown uses a non-existent Tailwind class "max-h-55" which is dropped by the
CSS build; replace "max-h-55" with a valid utility like "max-h-56" or an
arbitrary value "max-h-[13.75rem]" in the component rendering the suggestions
(look for the div containing "max-h-55 overflow-y-auto py-1" inside
TorrentDialogs's suggestions map and update the class there), and apply the same
fix for the two other occurrences in TorrentCreatorDialog.tsx and
AddTorrentDialog.tsx.

[nitrobass24]

CodeRabbit's max-h-55 finding — this class is already used in AddTorrentDialog.tsx (2 instances) and TorrentCreatorDialog.tsx (1 instance). I matched the existing pattern for consistency. Happy to update all 4 occurrences to max-h-56 if preferred, but that felt out of scope for this PR.

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify the existing usage of max-h-55 in the codebase
echo "=== Checking for max-h-55 usage in AddTorrentDialog.tsx ==="
rg "max-h-55" web/src/components/torrents/AddTorrentDialog.tsx -n -C 2

echo -e "\n=== Checking for max-h-55 usage in TorrentCreatorDialog.tsx ==="
rg "max-h-55" web/src/components/torrents/TorrentCreatorDialog.tsx -n -C 2

echo -e "\n=== Checking for max-h-55 usage in TorrentDialogs.tsx ==="
rg "max-h-55" web/src/components/torrents/TorrentDialogs.tsx -n -C 2

echo -e "\n=== Total count of max-h-55 usage in the codebase ==="
rg "max-h-55" web/src/ --count-matches

Length of output: 2011

---

@nitrobass24, you're absolutely right—I've confirmed max-h-55 appears in:

• AddTorrentDialog.tsx (lines 1332, 1410)
• TorrentCreatorDialog.tsx (line 67)
• TorrentDialogs.tsx (line 671 - your addition)

Following the existing pattern for consistency makes sense. Since this is pre-existing technical debt across multiple files, fixing all 4 occurrences together (either in this PR or a follow-up) would be cleaner than addressing just one. If you'd prefer to keep this PR focused and tackle it separately, I can help open a follow-up issue. Either approach works—your call!

---

🧬 Code Graph Analysis Results

• File: web/src/components/torrents/TorrentDialogs.tsx, approximate lines 120-136
  • Snippet (relevant portion):

    <div className="relative">
      <div className="absolute z-50 mt-1 left-0 right-0 rounded-md border bg-popover text-popover-foreground shadow-md">
        <div className="max-h-55 overflow-y-auto py-1">
          {suggestions.map((entry, idx) => (
            <button
              key={entry}
              type="button"
              title={entry}
              className={cn(
                "w-full px-3 py-2 text-sm hover:bg-accent hover:text-accent-foreground",
                highlightedIndex === idx
                  ? "bg-accent text-accent-foreground"
                  : "hover:bg-accent/70",
              )}
              onMouseDown={(e) => e.preventDefault()}
              onClick={() => handleSelect(entry)}
            >
              <span className="block truncate text-left">{entry}</span>
            </button>
          ))}
        </div>
      </div>
    </div>
    

  • Context: This is the autocomplete suggestion dropdown for Set Location (path autocomplete), where the container uses max-h-55 to cap height.

---

🧠 Learnings used

Learnt from: finevan
Repo: autobrr/qui PR: 677
File: web/src/components/torrents/AddTorrentDialog.tsx:496-504
Timestamp: 2025-12-03T18:11:08.682Z
Learning: In the AddTorrentDialog component (web/src/components/torrents/AddTorrentDialog.tsx), temporary path settings (useDownloadPath/downloadPath) should be applied per-torrent rather than updating global instance preferences. The UI/UX is designed to suggest that these options apply to the individual torrent being added.

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

web/src/components/torrents/TorrentManagementBar.tsx (1)

808-817: ⚠️ Potential issue | 🔴 Critical

Fix undefined safeInstanceId (build break)

safeInstanceId isn’t declared in this component, matching the TS2552 failure. Use an in-scope value such as actionInstanceId (or metadataInstanceId if that’s the intended semantics).

💡 Suggested fix

-        instanceId={safeInstanceId}
+        instanceId={actionInstanceId}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@web/src/components/torrents/TorrentManagementBar.tsx` around lines 808 - 817,
The prop instanceId passed to <SetLocationDialog> is using an undefined
identifier safeInstanceId causing the build error; replace safeInstanceId with
an in-scope identifier (e.g. actionInstanceId or metadataInstanceId depending on
intended semantics) used elsewhere in TorrentManagementBar so the instanceId
prop is defined; locate the <SetLocationDialog ... instanceId={safeInstanceId}
/> usage and change instanceId to actionInstanceId (or metadataInstanceId if you
need metadata context) and ensure any related handlers like
handleSetLocationWrapper and getCommonSavePath(selectedTorrents) still work with
the chosen instance id.

♻️ Duplicate comments (1)

web/src/components/torrents/TorrentDialogs.tsx (1)

628-636: Enter submission now respects autocomplete handling

Good guard against submitting when autocomplete consumes Enter.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@web/src/components/torrents/TorrentDialogs.tsx` around lines 628 - 636, You
correctly moved autocomplete handling before Enter-submit, but ensure
handleAutocompleteKeyDown actually prevents default when it consumes the Enter
key so the !e.defaultPrevented guard works; update the implementation of
handleAutocompleteKeyDown (and confirm it is memoized with useCallback) to call
e.preventDefault() or otherwise mark the event when autocomplete handles the
key, leaving the handleKeyDown logic (which checks supportsPathAutocomplete,
calls handleAutocompleteKeyDown(e), then checks e.key === "Enter" &&
!e.defaultPrevented && !isPending && location.trim()) as-is.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@web/src/components/torrents/TorrentManagementBar.tsx`:
- Around line 808-817: The prop instanceId passed to <SetLocationDialog> is
using an undefined identifier safeInstanceId causing the build error; replace
safeInstanceId with an in-scope identifier (e.g. actionInstanceId or
metadataInstanceId depending on intended semantics) used elsewhere in
TorrentManagementBar so the instanceId prop is defined; locate the
<SetLocationDialog ... instanceId={safeInstanceId} /> usage and change
instanceId to actionInstanceId (or metadataInstanceId if you need metadata
context) and ensure any related handlers like handleSetLocationWrapper and
getCommonSavePath(selectedTorrents) still work with the chosen instance id.

---

Duplicate comments:
In `@web/src/components/torrents/TorrentDialogs.tsx`:
- Around line 628-636: You correctly moved autocomplete handling before
Enter-submit, but ensure handleAutocompleteKeyDown actually prevents default
when it consumes the Enter key so the !e.defaultPrevented guard works; update
the implementation of handleAutocompleteKeyDown (and confirm it is memoized with
useCallback) to call e.preventDefault() or otherwise mark the event when
autocomplete handles the key, leaving the handleKeyDown logic (which checks
supportsPathAutocomplete, calls handleAutocompleteKeyDown(e), then checks e.key
=== "Enter" && !e.defaultPrevented && !isPending && location.trim()) as-is.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 479b5b6 and b310631.

📒 Files selected for processing (5)

• web/src/components/torrents/TorrentCardsMobile.tsx
• web/src/components/torrents/TorrentDialogs.tsx
• web/src/components/torrents/TorrentManagementBar.tsx
• web/src/components/torrents/TorrentTableOptimized.tsx
• web/src/hooks/usePathAutocomplete.ts

🚧 Files skipped from review as they are similar to previous changes (1)

• web/src/components/torrents/TorrentCardsMobile.tsx

[nitrobass24]

@s0up4200
Conflicts resolved. The only conflict was in usePathAutocomplete.ts — PR #1431 (already merged to develop, which this builds on top of) added Windows path separator support in selectSuggestion, while this PR had the simpler slash-only version. I kept develop's version with the separator detection logic.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@web/src/components/torrents/TorrentManagementBar.tsx`:
- Around line 815-816: The prop instanceId is currently using an undefined
identifier safeInstanceId which will throw; replace safeInstanceId with the
already-defined metadataInstanceId where SetLocationDialog (or the component
rendered at the snippet using instanceId and capabilities) is invoked so the
instance passed matches the source used to fetch capabilities
(metadataInstanceId) and avoid the ReferenceError.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 6a801c8a-1dec-4d62-9205-5547ebe50be0

📥 Commits

Reviewing files that changed from the base of the PR and between b310631 and f77ed82.

📒 Files selected for processing (5)

• web/src/components/torrents/TorrentCardsMobile.tsx
• web/src/components/torrents/TorrentDialogs.tsx
• web/src/components/torrents/TorrentManagementBar.tsx
• web/src/components/torrents/TorrentTableOptimized.tsx
• web/src/hooks/usePathAutocomplete.ts

🚧 Files skipped from review as they are similar to previous changes (3)

• web/src/components/torrents/TorrentCardsMobile.tsx
• web/src/components/torrents/TorrentTableOptimized.tsx
• web/src/hooks/usePathAutocomplete.ts

[nitrobass24]

Fixed ReferenceError in TorrentManagementBar.tsx — instanceId={safeInstanceId} referenced an undefined variable. Replaced with metadataInstanceId, which is already used to fetch capabilities in the same component.