WordPress.org

Make WordPress Core


Ignore:
Timestamp:
05/23/2016 06:53:05 PM (3 years ago)
Author:
DrewAPicture
Message:

Docs: Apply inline @see tags to hooks referenced in DocBlocks for core classes.

Applying these specially-crafted @see tags allows the Code Reference parser to recognize and link these elements as actions and filters.

See #36921.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/wp-includes/customize/class-wp-customize-nav-menu-setting.php

    r37518 r37539  
    7575     * Previous (placeholder) term ID used before creating a new menu.
    7676     *
    77      * This value will be exported to JS via the customize_save_response filter
     77     * This value will be exported to JS via the {@see 'customize_save_response'} filter
    7878     * so that JavaScript can update the settings to refer to the newly-assigned
    7979     * term ID. This value is always negative to indicate it does not refer to
     
    101101     * Status for calling the update method, used in customize_save_response filter.
    102102     *
    103      * When status is inserted, the placeholder term ID is stored in $previous_term_id.
    104      * When status is error, the error is stored in $update_error.
     103     * See {@see 'customize_save_response'}.
     104     *
     105     * When status is inserted, the placeholder term ID is stored in `$previous_term_id`.
     106     * When status is error, the error is stored in `$update_error`.
    105107     *
    106108     * @since 4.3.0
     
    448450     * Storage for data to be sent back to client in customize_save_response filter.
    449451     *
     452     * See {@see 'customize_save_response'}.
     453     *
    450454     * @access protected
    451455     * @since 4.3.0
     
    460464     *
    461465     * Any created menus will have their assigned term IDs exported to the client
    462      * via the customize_save_response filter. Likewise, any errors will be exported
     466     * via the {@see 'customize_save_response'} filter. Likewise, any errors will be exported
    463467     * to the client via the customize_save_response() filter.
    464468     *
Note: See TracChangeset for help on using the changeset viewer.