[Yi-111-a]

What does this PR do?

LazyFolderChooser interpolated the selected folder path straight into the /api/filesystem query string:

.$get(`/api/filesystem?path=${path}&level=${level}`)

A folder whose name contains & (also #, +) produced a request like ?path=H:/Audio & Books&level=1. The & terminates the path parameter, so the server only sees path=H:/Audio — a non-existent relative path — and answers 400 Invalid "path" query string. The UI then shows the "Failed to load data" toast and the subfolders never load.

Encoding the value with encodeURIComponent keeps the path in a single parameter. The server already receives a decoded value, because FileSystemController.getPaths reads req.query.path from Express' query parser, so no server-side change is needed.

This matches how the rest of the client builds query strings (e.g. search.vue, GlobalSearch.vue, Match.vue).

Where to review

client/components/modals/libraries/LazyFolderChooser.vue — single line, in fetchDirs.

Testing

• Verified the failing request shape: GET /api/filesystem?path=H:/Audio & Books&level=1 → 400.
• With encodeURIComponent, the same server returns the subfolders for a folder named Audio & Books.
• Client lint is clean (the client/ tree is covered by the repo's eslint ignore patterns, so no lint config changes are needed).

Related

• Fixes [Bug]: Folder chooser shows "Failed to load data" for folder names containing & # + (path not URL-encoded) #5642
• Same class of bug as [Bug]: (Match tab) If Search Title or Author contain &, search query is incorrectly encoded #2128 (match-tab search query not encoded).