[5.x] Add ignore option to CacheWatcher #1594
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request enhances the
CacheWatcherfunctionality in Telescope by introducing anignoreoption, allowing specific cache keys to be skipped. This addition provides greater flexibility in controlling which cache events are recorded.The motivation behind this feature was the realization that Telescope was recording
laravel:pulse:restartinto the database every second, consuming excessive disk space. Unfortunately, these records are not pruned with theprunecommand. Since this type of data is unnecessary for my use case, and there should be other use cases, I developed this option to exclude specific cache keys.