Changeset 10248 for trunk/src/bp-xprofile/classes/class-bp-xprofile-field.php

Timestamp:

10/11/2015 04:27:50 PM (10 years ago)

Author:

djpaul

Message:

phpdoc: remove obsolete @access public|protected|private statements.

These should only be used on procedural functions that, for legacy
reasons, pretend they are private by prefacing their name with an
underscore.

As modern PHP parsers and IDEs use reflections to figure out the
visibility scope of methods and properties by looking at the actual
code, there’s also no bonus in keeping these purely for documentation.

File:

• trunk/src/bp-xprofile/classes/class-bp-xprofile-field.php (modified) (3 diffs)

trunk/src/bp-xprofile/classes/class-bp-xprofile-field.php

@@ -126 +126 @@
      * @since 2.4.0 Property marked protected. Now accessible by magic method or by `get_default_visibility()`.
      *
-     * @access protected
      * @var string Default field data visibility.
      */
@@ -137 +136 @@
      * @since 2.4.0 Property marked protected. Now accessible by magic method or by `get_allow_custom_visibility()`.
      *
-     * @access protected
      * @var string Members are allowed/disallowed to modify data visibility.
      */
@@ -164 +162 @@
      *
      * @since 2.4.0
-     * @access protected
      * @var array Array of member types.
      */