Parent
#8 — Katalog-Route-Reads auf cachebare Store-API-GETs umstellen (Cache-Rework)
What to build
Upgrade the Shopware frontend stack to the versions that expose the cacheable GET read variants. This is the foundation every downstream ticket builds on. cacheableReads stays off/default here — behaviour is unchanged (all reads still POST), so the app stays green and backwards-compatible.
Scope note (resolved during implementation): the "regenerate typed GET operations" part was split out. The only cacheable catalog GET missing from the bundled @shopware/api-client@1.5 types is readLandingPageGet (the other five — category, product, product-listing, navigation, seo-url — are already typed). Adding it requires modernizing shopware.d.ts for api-client 1.5, which unmasks a set of pre-existing 1.5-migration type errors in app code. That work is tracked in #18 (kept out of this ticket to keep the deps upgrade a clean, zero-regression change). Regenerating via @shopware/api-gen against the available backend was rejected: it's an a4g customer instance and pollutes the schema with 100+ non-vanilla routes.
Acceptance criteria
Blocked by
- None — can start immediately
Follow-up
Parent
#8 — Katalog-Route-Reads auf cachebare Store-API-GETs umstellen (Cache-Rework)
What to build
Upgrade the Shopware frontend stack to the versions that expose the cacheable GET read variants. This is the foundation every downstream ticket builds on.
cacheableReadsstays off/default here — behaviour is unchanged (all reads still POST), so the app stays green and backwards-compatible.Scope note (resolved during implementation): the "regenerate typed GET operations" part was split out. The only cacheable catalog GET missing from the bundled
@shopware/api-client@1.5types isreadLandingPageGet(the other five — category, product, product-listing, navigation, seo-url — are already typed). Adding it requires modernizingshopware.d.tsfor api-client 1.5, which unmasks a set of pre-existing 1.5-migration type errors in app code. That work is tracked in #18 (kept out of this ticket to keep the deps upgrade a clean, zero-regression change). Regenerating via@shopware/api-genagainst the available backend was rejected: it's an a4g customer instance and pollutes the schema with 100+ non-vanilla routes.Acceptance criteria
@shopware/composables@1.12,@shopware/api-client@1.5,@shopware/nuxt-module@1.5,@shopware/helpers@1.7.1installed (+@shopware/api-gen@1.5devDep);composables/api-client/helperspromoted to direct depscacheableReadsremains unset (default off); no read changes from POST to GET in this ticketnpm lintpassesnpx nuxt typecheckintroduces no new errors vs. the pre-existing baseline (full green tracked separately in Clear pre-existing npx nuxt typecheck baseline (~124 errors) #17)...Getoperations: 5/6 already provided by bundled 1.5 types;readLandingPageGet+ the requiredshopware.d.ts1.5 modernization moved to Migrate shopware.d.ts to api-client 1.5 (typed operations + readLandingPageGet) and fix unmasked app types #18Blocked by
Follow-up
shopware.d.tsfor api-client 1.5 and addreadLandingPageGet