Part of meta-issue #1856630: [Change notice] [META] Rename Views methods to core standards
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | views_rename_getJoinData-2002924-14.patch | 2.41 KB | markie |
| #7 | views_rename_getJoinData-2002924-7.patch | 2.64 KB | markie |
| #1 | rename_get_join_data.2002924.1.patch | 2.41 KB | markie |
Comments
Comment #1
markie commentedpatched
Comment #3
markie commented#1: rename_get_join_data.2002924.1.patch queued for re-testing.
Comment #5
oenie commentedAdd public access modifier in front of the function to adhere to the new OOP standards.
Comment #6
oenie commentedComment #7
markie commentedadded public
Comment #8
markie commentedswitch to needs review..
Comment #10
markie commented#7: views_rename_getJoinData-2002924-7.patch queued for re-testing.
Comment #11
oenie commentedLooks good to me now !
Comment #12
alexpottNot sure I've seen this coding standard before. And looking at the function is appears it could be protected instead of public.
Comment #13
dawehnerThere is at least one module reverse_node_reference which calls this method in a public context.
Comment #14
markie commentedI went ahead and removed the line, but I don't see the harm in declaring the functions access in the documentation. It is a valid docblock tag, and was suggested by PHPStorm. Actually, I don't see anything in the Drupal Coding Standards about function documentation..
Comment #15
dawehnerThank you!
Well I don't see an advantage in using it, as @access doesn't really add additional information.
Comment #16
alexpottCommitted b58f444 and pushed to 8.x. Thanks!