For a coding standards cleanup, remove unused variables.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | views-remove_unsed_variables-3386717-6.patch | 59.49 KB | tibezh |
Issue fork views-3386717
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
damienmckennaHopefully this doesn't cause any regressions.
Comment #5
urvashi_vora commentedPlease review.
Thanks
Comment #6
tibezh commentedI've changed a little bit the ticket title and description.
Also prepared a patch to remove unused variables in the code. Just code refactoring.
Needs review.
Comment #7
joseph.olstadGreat work once again @tibezh
Comment #8
joseph.olstadComment #10
damienmckennaCommitted. Thanks everyone.
Comment #12
skylord commentedHm. After this commit views_handler_area_result is broken 'cause all variables referenced later with curly braces syntax were removed....
Comment #13
cboyden commentedAfter this commit, I'm getting out-of-memory errors on an existing view with a contextual filter.
Comment #14
trafo commentedIn
views_plugin_argument_validate_php::validate_argument()removed variables might be used in the actual PHP code that is evaluated witheval(). Like in my case. Would be nice to give at least warning to check that code.We noticed some regression also with exposed forms, but not sure if it's tight to this.
Comment #15
art4003 commentedAs @trafo mentioned above, we also had some regression with the PHP code eval().
As per the docs:
"... You may change the argument by setting "$handler->argument". You may change the title used for substitutions for this argument by setting "$handler->validated_title"."
We we using the $handler->argument to set/update the argument. After the update this started failing.