Closed (fixed)
Project:
Search API
Version:
8.x-1.x-dev
Component:
Framework
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
4 Aug 2025 at 11:18 UTC
Updated:
23 Aug 2025 at 12:14 UTC
Jump to comment: Most recent
Change record: Plugin implementations should use PHP attributes instead of annotations
I already had this implemented in #3523808: Fix failing pipelines but then decided to split it into a separate issue so it can be more thoroughly reviewed and tested.
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 #3
drunken monkeyOpened an MR with the code from #3523808: Fix failing pipelines.
Comment #4
borisson_This merge request looks great and I think we can merge this. Since the discovery of normal annotations is not yet disabled, this shouldn't impact any plugins out in the wild.
Comment #5
drunken monkeyThanks for the feedback, good to hear!
I think I’ll still leave it open for a few days more before merging, just to be on the safe side.
I also now stumbled over #3099471: Deprecate "hidden" definition key in favor of "no_ui", which I had forgotten but makes sense – all other of our plugin types now have a
$no_uiproperty, but processors only have$hidden, which we now had to make explicit. (Up to now we had silently accepted both.)The good thing about this move is that people will have to manually (or semi-manually) switch from annotations to attributes anyways, so now would probably be a perfect moment to switch to
$no_ui, if we want. Or to add both but deprecate$hiddenright away.Not sure whether the additional consistency is worth the hassle, though. Any opinions on this?
Comment #6
borisson_I think it's a good idea to do, but if we can create a rector rule, to automate the refactoring, it doesn't have to happen at the same time.
Comment #7
drunken monkeyYou’re probably right, no need to do both at the same time. Thanks!
Merged.