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
Create single caching layer for all static information (ie, DI config, "component" objects, etc.) #8329
Conversation
bfc330a
to
51c6c6d
Compare
Moving to 3.0, not needed for LTS version. |
50c0dc7
to
d4e1269
Compare
…he building logic in DI global.php.
…r through new INI config settings, [Cache] static_cache_backend. The setting, for now, has no effect.
…al, StaticCacheFactory. The class is reused in DI config so only one cache will be created per backend type.
… data (this is the recommended cache per php-di's docs).
…use for VisitDimensions as proof of concept.
…hat shouldn't be instantiated immediately and use DI to load list of commands.
…ponents and replace uses w/ components.etc... DI key.
…nt with DI and remove related unneeded code in both classes.
d4e1269
to
de37d52
Compare
Thank you for this proposed pull request. Because it was last updated more than one month ago, it is our policy to close pull requests opened for a long time without updates. If you would like to continue work on the pull request, please simply ping us to have it re-opened (after you have pushed a new commit). We hope you understand this and we look forward to seeing an update from you on this pull request or another one! Thanks. |
Work in progress.
This PR intends to use a proper cache for the DI container so definitions will be cached, and to replace all other caches for 'static' information (such as Dimensions, Reports, etc.) w/ DI. This should create a single caching layer for this information that users can configure through INI config.
TODO: