# Tests/checks we need to complete to release a Stable/Beta V5 ## Core Rest-Cache Features ### Provider - [x] Check all providers function and can be loaded - [x] Confirm default provider (memory) loads correctly on boot - [x] Check getTimeout for providers function ### Strategy Options - [x] Ensure `debug` works - [x] Ensure `enableEtag` works and etags are generated - [x] Ensure `enableXCacheHeaders` works and headers are send on response - [x] Ensure `enableAdminCTBMiddleware` works (possibly rename since it's wrong?) and changes in admin bust cache properly - [ ] Ensure `resetOnStartup` works and is properly reset with all providers - Bug with Redis where the provider isn't initialized when it tries to reset - [x] Ensure `clearRelatedCache` functions even with deeply nested relations (test up to 10 levels) - [x] Ensure `keysPrefix` works and prefix is set properly (really only matters with Redis provider) - [ ] Ensure `hitpass` works -> we **may** skip this for now as it's complex - Skipped - [x] Ensure `maxAge` works and cache is auto-busted / set by default ### Cache Keys Global - [x] Ensure `useQueryParams` functions - [ ] Ensure `useHeaders` functions - Not working but we can ignore, not sure if this was ever working ### Content-types - [x] Ensure generic arrays functions `[ "api::test.test" ]` - [x] Ensure complex arrays functions `[ { "contentType": "api::test.test", ... } ] - [x] Ensure `injectDefaultRoutes` functions - [x] Ensure non-global options work (see Strategy Options) ### Custom Routes - [x] Check if limit to single-types is still in place or if we can add support for collection-types -> NICE TO HAVE NOT REQUIRED - Looks like caching and busting of single types is working as it does with collection-types :) ### Admin Panel - [x] Bust on update (including related) - [x] Bust via edit view - [x] Bust via list view ### Memory Provider - [x] Check `maxSize` functions - [ ] Document breaking change of `max` -> `maxSize` - [x] Check `maxAge` functions ### Redis Provider - [x] Ensure `connection` parameter load the `default` connection from `@strapi-community/plugin-redis` - [ ] Document breaking changes from `@strapi-community/plugin-redis` - [x] Ensure all ioredis options function (ttl, various server types, ect) - [ ] Possibly add a check/warning to ensure redis plugin config comes before rest-cache?
Tests/checks we need to complete to release a Stable/Beta V5
Core Rest-Cache Features
Provider
Strategy Options
debugworksenableEtagworks and etags are generatedenableXCacheHeadersworks and headers are send on responseenableAdminCTBMiddlewareworks (possibly rename since it's wrong?) and changes in admin bust cache properlyresetOnStartupworks and is properly reset with all providersclearRelatedCachefunctions even with deeply nested relations (test up to 10 levels)keysPrefixworks and prefix is set properly (really only matters with Redis provider)hitpassworks -> we may skip this for now as it's complexmaxAgeworks and cache is auto-busted / set by defaultCache Keys Global
useQueryParamsfunctionsuseHeadersfunctionsContent-types
[ "api::test.test" ]injectDefaultRoutesfunctionsCustom Routes
Admin Panel
Memory Provider
maxSizefunctionsmax->maxSizemaxAgefunctionsRedis Provider
connectionparameter load thedefaultconnection from@strapi-community/plugin-redis@strapi-community/plugin-redis