Skip to content

fix: preserve nested project tree in org projects when search is active #939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
timbastin merged 1 commit into from
Sep 16, 2026
Merged

fix: preserve nested project tree in org projects when search is active #939

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions src/hooks/useOrgProjects.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,13 +23,18 @@ export const useOrgProjects = (
async (requestUrl: string) => {
const data = await fetcher<Paged<ProjectDTO>>(requestUrl);
// the list endpoint returns plain projects; the nested tree is fetched
// lazily, so drop it here rather than pretend it is the frontend shape
// lazily, so drop it here rather than pretend it is the frontend shape.
// when searching, the endpoint already returns the tree, so keep it.
return {
...data,
data: data.data.map(({ subGroupsAndAsset: _nested, ...item }) => ({
...item,
resourceType: "project" as const,
})),
data: data.data.map(
({ subGroupsAndAsset, ...item }) =>
({
...item,
resourceType: "project" as const,
...(isSearchActive ? { subGroupsAndAsset } : {}),
}) as SubGroupsAndAsset,
),
} satisfies Paged<SubGroupsAndAsset>;
},
{ keepPreviousData: true },
Expand Down
Loading