Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
block.module
Priority:
Major
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
9 Mar 2015 at 19:33 UTC
Updated:
24 Mar 2015 at 09:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
berdirAnd here's a patch.
Comment #2
berdirThe code comment alone kind of shows how little sense those cache tags make. How on earth do you "modify a plugin"? change the code? :)
Comment #3
fabianx commentedIt is probably so that you could e.g. configure different text for different instances via config or such?
As a block:[foo] is one instance of a block plugin, but the plugin could have something central to apply to all such ...
That said, _if_ a block plugin in contrib wants to do so, they can just add the getCacheTags() method and be done, no need to default for all of those. when its not used in core.
As that:
RTBC, if tests pass
Could use a beta eval, too.
Comment #4
wim leers+100 — see #2241377-34: [meta] Profile/rationalise cache tags.
Exactly!
Comment #5
alexpottRemoving stuff that we are not using and makes no sense reduces fragility because we have less to maintain and test. Committed 809854e and pushed to 8.0.x. Thanks!