Make Cache keys accept backed enums

[ImSketch]

When you have a big project with a lot of cached data, failing to consistently use the correct keys when creating and reading data can become a maintenance and debugging nightmare. You might end up duplicating data or, even worse, misspelling a key and getting null even when valid data exists.

I think it's necessary for the Cache facade and its helper functions to accept backed enums to avoid the default behavior, that works pretty well but can be less debuggable.

Example:

// app\Enums\QuestionsAvailable.php
namespace App\Enums\QuestionsAvailable;

enum QuestionsCacheKeys: string
{
     case ClinicalCases = 'clinical_cases';
     case QuirurgicalCases = 'quirurgical_cases';

     public function byId(int $id): string
     {
         return match ($this) {
             QuestionsCacheKeys::ClinicalCases => "clinical_cases_{$id}",
             QuestionsCacheKeys::QuirurgicalCases => "quirurgical_cases_{$id}"
         };
     }

}

// ../../someFile.php
use App\Models\Question;
use Illuminate\Support\Facades\Cache;
use App\Enums\QuestionsCacheKeys;

Cache::get(QuestionsCacheKeys::ClinicalCases, Question::query()->where('type', 'clinical_case')->get());

Cache::remember(QuestionsCacheKeys::QuirurgicalCases, 3200, function () {
     return Question::query()->where('type', 'quirurgical_case')->get();
});

[henzeb]

it should also accept unit enums, as this is the perfect usecase for this. backed enums are generally for storing data, unit enums not, and even though it is the key that also gets stored, I don't think it is going to be an issue here.

[ImSketch]

You're right, both options will do the trick. I opted to write the idea based on backed enums because in some cases it's necessary to use a specific key (and not let the framework intuit it based on the name of the enum case).