Problem/Motivation
This class uses a class property for static caching, but it's a very thin wrapper around the cache collector which also does static caching. Probably we had this before we added the cache collector.
We can make library.discovery just be the cache collector itself without the extra service/class, less indirection.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | 3462871-nr-bot.txt | 1.77 MB | needs-review-queue-bot |
| #6 | 3462871-nr-bot.txt | 3.82 KB | needs-review-queue-bot |
Issue fork drupal-3462871
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
catchComment #4
catchThe test coverage removed here was added in #2378263: hook_library_alter() must be manually invoked by users of LibraryDiscovery, and has no test coverage, this add a hook_library_alter:
Then we removed hook_library_alter() in #2472547: Remove deprecated hook_library_alter() and the test was left testing the static caching in LibraryDiscovery, but without checking whether it was still necessary or not.
Comment #5
catchLet's do the deprecation here.
Once it's merged, a couple of the methods are redundant, so we should probably deprecate those too, but maybe those in a follow-up.
Comment #6
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #7
catchComment #8
catchErrm, needs review.
Comment #9
smustgrave commentedDeprecation seems fine, version wise.
Not 100% if all deprecations need a test to make sure the deprecation is returned. I feel like we know that feature works.
Comment #10
catchGenerally I think we should not do this, and only test deprecations triggered by actual backwards compatibility logic rather than from within deprecated code that's going to be removed. It takes time to write the test, run them every CI run, then remove them again, and they don't tell us much.
Comment #11
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #12
nod_bot has issues
Comment #14
nod_Committed 1c7a0b5 and pushed to 11.x. Thanks!
Comment #16
nod_Comment #20
nod_had to fix the commit since #3460598: Single directory component CSS asset library not picked up in admin theme immediately after module install without cache clear introduced a new use of the deprecated method