Using $this->t() instead of t() in this popular plugin type sets an example for all contrib plugins. (And replacing t() with $this->t() gets us very close to being able to unit test filter plugins, because all that's left then is the coupling with the filter.module process callback functions.)
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | filter-plugins-no-more-t-2165427-4.patch | 18.5 KB | eric_a |
| #1 | filter-plugins-no-more-t-2165427-1.patch | 18.5 KB | eric_a |
Comments
Comment #1
eric_a commentedComment #2
eric_a commentedComment #3
martin107 commentedPatch no longer applies.
Comment #4
eric_a commentedRerolled for #2203407: Replace #attached library array values with provider-namespaced strings where the following change happened.
Comment #5
sutharsan commentedCheck for remaining
t()usage after applying the patch. None found.Patch still applies.
I have no comments on the patch.
Comment #6
sutharsan commentedInspired by this issue, I've continued with block plugins: #2223435: Do not use t() in block plugins anymore
Comment #8
eric_a commented4: filter-plugins-no-more-t-2165427-4.patch queued for re-testing.
Comment #9
eric_a commentedFailure in #7 was absolutely unrelated to this patch:
Requeued and back to RTBC.
Comment #10
webchickThis is just code clean-up, so doesn't really fit as major. I'll get back to this shortly, doing a quick triage of the queue.
Comment #11
webchickOk, here we go!
Committed and pushed to 8.x. Thanks!