Herstructureer src/ naar feature-based folderstructuur
Continuous Integration / config (pull_request) Successful in 10s
Continuous Integration / prepare (pull_request) Successful in 1m26s
Continuous Integration / build-production (pull_request) Skipped
Continuous Integration / build (pull_request) Successful in 2m6s
Continuous Integration / test (pull_request) Successful in 2m2s
Continuous Integration / deploy-production (pull_request) Skipped
Deploy / deploy (pull_request) Successful in 38s
Continuous Integration / deploy-test (pull_request) Successful in 39s

Volgt de aanpak uit het React 2025 folder structure artikel en het
SlpModularCms/frontend referentieproject: components/{layout,ui,shared},
features/landing/{components,data,hooks,pages,__tests__}, en lib/ voor
de query client. routes/index.tsx wordt een dunne wrapper rond de nieuwe
features/landing/pages/LandingPage.tsx.
This commit is contained in:
2026-08-01 00:10:21 +02:00
parent a3ecfec668
commit 0037b0d304
25 changed files with 34 additions and 33 deletions
@@ -0,0 +1,19 @@
import { useQuery } from '@tanstack/react-query';
import { packages, type PackageCardData } from '../data/content';
/**
* Placeholder query hook (requirements FR-5). The queryFn currently just resolves the
* static package data, wrapped in a Promise so the calling component already consumes
* it exactly the way it will once a real API exists — only this queryFn's body will
* need to change in a future iteration.
*/
async function fetchPackages(): Promise<PackageCardData[]> {
return Promise.resolve(packages);
}
export function usePackagesQuery() {
return useQuery({
queryKey: ['packages'],
queryFn: fetchPackages,
});
}