Skip to content
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

feat(http): Create memory cache provider #33900

Merged
merged 2 commits into from
Feb 10, 2025

Conversation

zharinov
Copy link
Collaborator

@zharinov zharinov commented Jan 28, 2025

Changes

We want to cache http requests in memory selectively, instead of caching all GET/HEAD responses.
This PR creates class which should be used when this kind of caching is needed.

Context

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@zharinov zharinov requested review from viceice and rarkins January 28, 2025 17:36
@zharinov zharinov marked this pull request as draft January 28, 2025 18:35
@viceice viceice removed request for viceice and rarkins January 31, 2025 09:01
@zharinov zharinov marked this pull request as ready for review February 10, 2025 15:13
@zharinov zharinov requested review from rarkins and viceice February 10, 2025 15:13
@viceice viceice added this pull request to the merge queue Feb 10, 2025
Merged via the queue into renovatebot:main with commit 1e702c2 Feb 10, 2025
41 of 56 checks passed
@viceice viceice deleted the feat/http-memory-cache-provider branch February 10, 2025 16:25
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 39.165.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

4 participants