{"issue":{"state":"open","created_at":"2011-11-28T06:22:10Z","updated_at":"2011-11-28T10:45:53Z","user":{"gravatar_id":"196fcecb9032f580dbed8d06a3aac090","id":789929,"url":"https://api.github.com/users/tomykaira","avatar_url":"https://secure.gravatar.com/avatar/196fcecb9032f580dbed8d06a3aac090?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"tomykaira"},"comments":1,"body":"At first, thanks to new twitter-gem 2.0.0.  I appreciate getting rid of Hashie, because class expansion became much easier.\r\n\r\nMy question is why some of attrs are not made visible by `lazy_attr_reader`.\r\n\r\nFor example, Twitter::Status has reader methods `in_reply_to_screen_name`, `in_reply_to_attrs_id` and `in_reply_to_user_id`, but does not have `in_reply_to_status_id`.\r\n\r\nIs this just a bug, or based on some intention?\r\n\r\n","assignee":null,"id":2364417,"labels":[],"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"number":214,"title":"Why some attrs are not accessible via a reader method?","closed_at":null,"html_url":"https://github.com/jnunemaker/twitter/issues/214","url":"https://api.github.com/repos/jnunemaker/twitter/issues/214","milestone":null},"action":"created","comment":{"created_at":"2011-11-28T10:45:53Z","updated_at":"2011-11-28T10:45:53Z","user":{"gravatar_id":"1f74b13f1e5c6c69cb5d7fbaabb1e2cb","id":10308,"url":"https://api.github.com/users/sferik","avatar_url":"https://secure.gravatar.com/avatar/1f74b13f1e5c6c69cb5d7fbaabb1e2cb?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"sferik"},"body":"That's a bug. Good find.\r\n\r\nIt's an artifact of an earlier design, in which there was a `Twitter::Status#in_reply_to_status` method that returned a `Twitter::Status`, which would have made `in_reply_to_status_id` unnecessary, since you could call `in_reply_to_status.id` instead.\r\n\r\nWhen I removed the `in_reply_to_status` method, I forgot to add `in_reply_to_status_id` to the list of `lazy_attr_reader`s.\r\n\r\nThis, of course, is one of the downsides of moving away from hashie. :\\\r\n\r\nI'm planning on pushing 2.0.1 shortly, which will contain the fix and a few others.","id":2895374,"url":"https://api.github.com/repos/jnunemaker/twitter/issues/comments/2895374"}}