Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4020c536c7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| } | ||
| return kinds; | ||
| }, [fileBrowser.fileArray]); | ||
| const displayFileArray = fileBrowser.fileArray.map((entry) => ({ ...entry, path: toDisplayPath(entry.path) })); |
There was a problem hiding this comment.
Add missing ancestor nodes after remapping display paths
When queryBasePath is a descendant of displayBasePath, this remap turns entries like /child into /subdir/child but does not materialize the new ancestor (/subdir) in the list. useFileBrowser already drops the query root entry, so FileTree ends up with no root-level nodes and renders an empty browser for snapshots whose base paths differ (for example, include-path snapshots shown against a volume root). That makes restore/download selection impossible in that flow.
Useful? React with 👍 / 👎.
4020c53 to
187030d
Compare
187030d to
28d5c05
Compare

Closes #709