h3ravel/framework

Feat: Integrate Cacheable for cache management

Open

#2 opened on Aug 2, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (14 forks)auto 404
@h3ravel/cacheFeature Requirementenhancementhelp wantedperformance

Repository metrics

Stars
 (22 stars)
PR merge metrics
 (PR metrics pending)

Description

Background: Applications need a unified caching layer to improve performance and reduce redundant computations. Integrating Cacheable (or similar) will provide a consistent API for working with different cache backends like memory, Redis, or database.

Tasks:

  • Add Cacheable as dependency.
  • Add your implementation to the framework/cache package directory
  • Implement CacheManager to configure and manage multiple cache stores.
  • Provide drivers for memory and redis out of the box.
  • Add helpers for common operations: put, get, forget, remember.
  • Add support for tagging and TTL (time-to-live).
  • Write unit tests for each driver and helper.
  • Document cache usage with examples.

Acceptance criteria:

  • Developers can configure cache stores in config (memory, redis, etc.).
  • Interface mirrors laravel as much as possible, creating the familiar DX while also adding it own unique twists and turns.
  • Cache.put stores and expires values as expected.
  • Cache.remember fetches from cache or computes and stores if missing.
  • Tests validate behavior across drivers.

Difficulty: medium

Contributor guide

Research direction
Study the framework's existing cache directory structure, then explore the Cacheable library API. Create a CacheManager class that supports memory and redis drivers, implementing put, get, forget, remember, tagging, and TTL. Write unit tests for each driver.
Tech stack
typescript
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60