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: Give more control over caching #40860

Closed
wants to merge 1 commit into from

Conversation

ChristophWurst
Copy link
Member

Summary

  • Make it clear when caching is actually available and populating makes sense
  • Add factory method for in-memory caches

This is quick PR putting some ideas around #40800 into code.

Checklist

* Make it clear when caching is actually available and populating it
  makes sense
* Add factory method for in-memory caches

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
@ChristophWurst ChristophWurst added 2. developing Work in progress feature: caching Related to our caching system: scssCacher, jsCombiner... labels Oct 11, 2023
@ChristophWurst ChristophWurst self-assigned this Oct 11, 2023
@solracsf solracsf added this to the Nextcloud 28 milestone Oct 27, 2023
@skjnldsv skjnldsv mentioned this pull request Nov 1, 2023
@ChristophWurst ChristophWurst removed this from the Nextcloud 28 milestone Nov 2, 2023
@ChristophWurst
Copy link
Member Author

There are method to check availability before acquiring an instance. This isn't strictly required.

@ChristophWurst ChristophWurst deleted the feat/caching-control branch November 2, 2023 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2. developing Work in progress feature: caching Related to our caching system: scssCacher, jsCombiner...
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants