Skip to content

Provide option to limit number of cached entries per key #121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

tjwallace
Copy link

Related #112

@tjwallace tjwallace force-pushed the storage_max_entries branch from 978572e to 6d2f119 Compare October 1, 2020 19:29
@tjwallace tjwallace changed the title Provide option to maximum number of cached entries per key Provide option to limit number of cached entries per key Oct 1, 2020
@@ -83,6 +83,7 @@ class HttpCache < Faraday::Middleware
# :instrumenter - An instrumentation object that should respond to 'instrument'.
# :instrument_name - The String name of the instrument being reported on (optional).
# :logger - A logger object.
# :max_entries - The maximum number of entries to store per cache key.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe a better name would be max_entries_per_(cache_)key?

@garaujodev
Copy link
Contributor

@tjwallace I'm sorry for the late reply on this PR. I'm assuming as a maintainer.

If you still interested on this solution: You can rebase this PR and solve the conflicts?

@garaujodev garaujodev closed this Jun 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants