Eliminate cache busting

Solid is a REST API, so request URIs are treated as names of resources. A cache breaker bogus query string parameter could be interpreted by a Solid server as a different name. Indeed it was handled thus by ESS, so Pod Spaces requests were failing. This change fixes that issue.

In generatl I highly recommend getting the core application working first without the added complexity of caching. Once the core features are stable, you might consider adding caching.

Author: langsamu

app/lib/hooks/useBrowseStorage.ts

@@ -104,7 +104,7 @@ export function useBrowseStorage(containerUrl: string | null, refreshKey?: numbe
 
         // Use @inrupt/solid-client to fetch the container dataset
         const containerDataset = await getSolidDataset(url, {
-          fetch: fetchWithCacheBust,
+          fetch: fetchFn,
         });
 
         // Get all contained resource URLs using @inrupt/solid-client
@@ -128,7 +128,7 @@ export function useBrowseStorage(containerUrl: string | null, refreshKey?: numbe
             // If refreshKey is provided, fetch .meta files to get updated names after rename/upload
             if (refreshKey !== undefined) {
               try {
-                const metaName = await getDisplayNameFromMeta(absoluteUrl, fetchWithCacheBust);
+                const metaName = await getDisplayNameFromMeta(absoluteUrl, fetchFn);
                 if (metaName) {
                   name = metaName;
                 }
@@ -177,7 +177,7 @@ export function useBrowseStorage(containerUrl: string | null, refreshKey?: numbe
             if (!isContainerUrl && !isLikelyFile(absoluteUrl)) {
               try {
                 const itemDataset = await getSolidDataset(absoluteUrl, {
-                  fetch: fetchWithCacheBust,
+                  fetch: fetchFn,
                 });
                 finalIsContainer = isContainer(itemDataset);
               } catch (e) {