Summary

This PR refactors the cache configuration structure to follow Laravel's convention with a stores-based pattern, improving flexibility and consistency with other modern PHP frameworks.

Changes

Configuration Structure (src/cache/publish/cache.php)

• Introduced default key for driver selection with environment variable support (CACHE_DRIVER)
• Moved cache configurations under stores array
• Maintained backward compatibility with existing driver configurations

CacheManager Updates (src/cache/src/CacheManager.php)

• Modified getDriver(?string $name = null) to accept null parameter and read from default config
• Updated config resolution path from cache.{$name} to cache.stores.{$name}
• Improved call() method with proper type hints and simplified parameter signature
• Better separation of concerns between driver selection and configuration retrieval

Test Updates (src/cache/tests/Cases/RedisDriverTest.php)

• Updated test configurations to match new structure
• Ensured all existing tests pass with the new configuration format

Benefits

• Better Organization: Clearer separation between default driver selection and store configurations
• Framework Consistency: Aligns with Laravel's caching conventions, making it easier for developers familiar with Laravel
• Environment Configuration: Native support for CACHE_DRIVER environment variable
• Flexibility: Easier to manage multiple cache stores and switch between them
• Maintainability: More intuitive structure for future enhancements

Migration Guide

Users need to update their config/autoload/cache.php file from:

return [
    'default' => [
        'driver' => RedisDriver::class,
        'packer' => PhpSerializerPacker::class,
        'prefix' => 'c:',
    ],
];

To:

return [
    'default' => env('CACHE_DRIVER', 'default'),
    'stores' => [
        'default' => [
            'driver' => RedisDriver::class,
            'packer' => PhpSerializerPacker::class,
            'prefix' => 'c:',
        ],
    ],
];

Test Plan

• Existing unit tests updated and passing
• Verified CacheManager correctly resolves default driver
• Tested environment variable configuration
• Confirmed backward compatibility with driver selection
• Manual testing with different cache stores recommended
• Verify in production-like environment before merging