Existing multicaching support not exposed in types

[adworacz]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Technically, the code supports multicaching, as written here: https://github.com/nestjs/cache-manager/blob/master/lib/cache.providers.ts#L53-L59

However, the types set on the register function do not indicate any sort of array input support.

There's also no mention of multicaching support in the documentation

Minimum reproduction code

https://github.com/nestjs/cache-manager/blob/master/lib/cache.providers.ts#L53-L59

Steps to reproduce

No response

Expected behavior

Multicaching should be supported by the register and registerAsync methods.

Package version

2.0.1

NestJS version

10.0.5

Node.js version

No response

In which operating systems have you tested?

• macOS
• Windows
• Linux

Other

No response

[kamilmysliwiec]

Would you like to create a PR for this issue?

[adworacz]

I'm open to doing so. I'm not sure when I can invest the time just yet, got a few critical projects that need to see completion in the coming month.

[Djunnni]

hello there 👋🏻
let you know more situation about this problem. if i can understand that. i want to try :)

[honguyenhaituan]

Hi @Djunnni,

There exists a way to set up multi-caching. I saw it in the test case:

cache-manager/tests/src/multi-store/multi-store.module.ts

Lines 8 to 21 in 2a82f89

	CacheModule.register([
	{
	store: 'memory',
	max: 100,
	ttl: 50,
	},
	{
	store: redisStore,
	host: 'localhost',
	port: 6379,
	db: 0,
	ttl: 50,
	},
	]),

But I think it is very hard to read CacheModuleOptions to know there is an existing way config like that.

cache-manager/lib/interfaces/cache-module.interface.ts

Lines 4 to 15 in 2a82f89

	export type CacheModuleOptions<
	StoreConfig extends Record<any, any> = Record<string, any>,
	> =
	// Store-specific configuration takes precedence over cache module options due
	// to how `createCacheManager` is implemented.
	CacheManagerOptions &
	StoreConfig & {
	/**
	* If "true', register `CacheModule` as a global module.
	*/
	isGlobal?: boolean;
	};

So I suggest changing the type of CacheModuleOptions so everyone can easily set up when using the lib.