Weave Code
Cache Bundle Laravel Package
rich-id/cache-bundle
A Laravel/PHP cache bundle for rich-id that helps store and reuse resolved identifier data, reducing repeated lookups and speeding up responses. Install with Composer, point it at your preferred cache store, and add caching to your rich-id workflow with minimal configuration.
At a glance
Frequently asked questions about Cache Bundle
- What does rich-id/cache-bundle do in a Laravel application?
- It is a Laravel/PHP cache bundle for rich-id that stores and reuses resolved identifier data so your application does not repeat the same lookups. The overview describes adding caching to a rich-id workflow with minimal configuration after installing via Composer and pointing it at a cache store. The package is at v0.1.x, so review the source and test it in your own stack before relying on it in a hot path.
- How do I install rich-id/cache-bundle with Composer?
- Install it as a Composer dependency in your Laravel project, typically with composer require rich-id/cache-bundle. For a pilot or production evaluation, pin the exact version, for example "rich-id/cache-bundle": "0.1.2", rather than using a caret range at 0.x. Then publish or add any configuration the package provides for your chosen cache store.
- How do I configure the cache store used by rich-id/cache-bundle?
- The overview says to point the bundle at your preferred cache store and add caching with minimal configuration, but it does not include the exact config keys. Check the package config file and README after installation, and confirm whether it uses Laravel's default cache store or a dedicated store connection. If a cache prefix is configurable, version it so old and new entries cannot collide during deploys.
- Which Laravel and PHP versions does rich-id/cache-bundle support?
- The provided release context does not document a supported Laravel or PHP version matrix. Before installing, inspect the Composer constraints in the package's composer.json and avoid constraints that pin Laravel to a narrow minor line. Also check which cache drivers are actually exercised in CI, because an array-driver test does not prove Redis, database, file, or memcached behavior.
- What changed in rich-id/cache-bundle v0.1.2 for caching null values?
- The v0.1.2 release note says "Fix caching null value," which points to the common cache-miss versus cached-null correctness problem. The release note does not state whether null is now cached using a sentinel or treated as a miss, and those are opposite behaviors for negative caching. Review the source and add a regression test for your null round-trip before upgrading.
- Do I need to flush the cache after upgrading rich-id/cache-bundle to v0.1.2?
- You should plan an explicit cache flush or key-prefix bump as part of the deploy, because the null-handling fix may have changed stored semantics. The release note does not say whether the serialization format or cache key structure changed. If entries from older versions are unreadable or interpreted differently, stale data can surface as incorrect application behavior.
- Is rich-id/cache-bundle safe to use in production at version 0.1.x?
- It is pre-1.0 software, so SemVer does not guarantee stability across minor releases and a caret constraint can opt you into breaking changes. Caching bugs also tend to be silent: they return stale or incorrect data rather than throwing an exception. Treat it as greenfield, pin an exact version for the pilot, and test the null and invalidation paths in a staging environment first.
- How should I test rich-id/cache-bundle in a Laravel application?
- At minimum, test a cache miss, a cached real value, and a cached null round-trip, because the v0.1.2 fix targets that edge case. Run those tests against the cache driver you actually use in production, not only the array driver. Also test cache invalidation, TTL expiry, and behavior during a rolling deploy where old and new code share the same cache.
- Does rich-id/cache-bundle support cache tags and multiple cache drivers?
- The available overview does not confirm tag support or list which Laravel cache drivers are supported and tested. If you rely on tags, verify that the package wraps Illuminate\Contracts\Cache\Repository cleanly and does not assume a specific driver's semantics for null, TTL, or tags. Test with your production driver, such as Redis or database, before committing.
- What are alternatives to rich-id/cache-bundle for caching identifier lookups?
- You can use Laravel's Cache::remember directly around your rich-id resolution calls, or write a small cache decorator or repository wrapper that matches your lookup contract. The main advantage of a dedicated package is ready-made integration and null handling; the main advantage of your own wrapper is full control over keys, TTL, invalidation, and drivers. Compare maintenance burden and test coverage before adding another dependency to a hot path.
Weaver
How can I help you explore Laravel packages today?