[wp-trac] [WordPress Trac] #36946: Provide `id` properties on core objects

WordPress Trac noreply at wordpress.org
Thu May 26 03:45:12 UTC 2016


#36946: Provide `id` properties on core objects
--------------------------+-----------------------------
 Reporter:  jeremyfelt    |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+-----------------------------

Comment (by jeremyfelt):

 Replying to [comment:4 dd32]:
 > Replying to [comment:3 DrewAPicture]:
 > > All that aside, per the linked discussion, I ''really'' don't think a
 deprecated notice or a `_doing_it_wrong()` is a good idea, considering our
 history and the fact that `$user->ID` and `$post->ID` are used ''all
 over'' the WordPress ecosystem.
 >
 > I '''really''' agree with this, I don't think we should be firing
 deprecated notices for ''everything'' but rather just have the different-
 case'd variants "just work". There's zero harm in using `->ID` over
 `->id`, it's not like we're ever going to remove the `ID` versions.

 Agreed. I don't think we need to deprecate anything. Just un-deprecate
 `WP_User::id`. :)

--
Ticket URL: <https://core.trac.wordpress.org/ticket/36946#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list