Closed (fixed)
Project:
Drupal core
Version:
10.1.x-dev
Component:
views.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
25 Jul 2022 at 23:13 UTC
Updated:
13 Mar 2023 at 15:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
andypostComment #3
andypostProbably magic __get()/__set() could help here but could have override in contrib/custom code
Comment #4
andypostlet's see baseline
Comment #5
andypost519 fail
Comment #6
andypostAs \Drupal\views\ViewExecutable::_preQuery() assigning
positionproperty for every views' plugin I moved the definition toPluginBaseas the property was added to\Drupal\views\Plugin\views\argument\ArgumentPluginBase::$positionin #3295157: Fix 'Access to an undefined property' PHPStan L0 errors - public propertiesPatch should fix a lot of tests
Comment #7
andypostChecking remains, the
$render_tokenswhich is used only by\Drupal\views\Plugin\views\field\FieldPluginBaseso renamed and looking for reviewsComment #8
andypostAnd a bit more
and
Comment #9
andypostAttempt to fix, looks better to split every property into own issue
Comment #10
andypostIt's an array of strings
Comment #12
lendude@andypost asked me to chime in with an opinion, so here it is.
These @see everywhere are very helpful now, but will at some point get hopelessly outdated since we will never ever remember to update them when the code being referred to changes for whatever reason. So do we really want these? No idea how they were done in other issues like this one.
I'm fine with renaming the variables to camelcase, but this could be considered a BC break. This being Views, there is a high possibility that somebody somewhere is making use of these variables under their current name in a way we don't expect.
Will a change record suffice or should we do deprecation errors (which might be tricky)? We need an answer on that.
Setting to needs work to get a documented decision on these questions.
Comment #13
andypostThere's some usage in contrib
- http://codcontrib.hank.vps-private.net/search?text=validated_title
- http://codcontrib.hank.vps-private.net/search?text=render_tokens
so I reverted it and tuned docblocks, let's see if sniffers will allow it (I gonna explore
DeprecatedServicePropertyTraitmeantime)That's looks minimal patch
let's do rename via #2052421: [META] Rename Views properties to core standards
Comment #14
andypostSpecific follow-ups are
-
validated_titleexisting #2062177: In ArgumentPluginBase Rename Views properties to core standards-
render_tokensfiled #3344578: In StylePluginBase Rename Views properties to core standardsComment #15
lendudeNice and minimal and the follow ups look good to me.
Comment #16
catchCommitted ab9bb57 and pushed to 10.1.x. Thanks!
Comment #18
catch