{"comment":{"position":13,"user":{"avatar_url":"https://secure.gravatar.com/avatar/e145b50faf662e70c066b13c98921900?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"e145b50faf662e70c066b13c98921900","url":"https://api.github.com/users/aphyr","login":"aphyr","id":3748},"updated_at":"2011-11-11T16:32:40Z","commit_id":"a1e40c57ddde3c138cb5f6bde6e5fa5573c6d8ff","url":"https://api.github.com/repos/seancribbs/ripple/comments/711411","line":31,"body":"Shoot! I didn't think of that. Personally, I feel that unsupported options should be ignored silently,  because it lets me pass options hashes down through multiple layers of code without tight coupling. How do you guys feel? Bring back valid-options or kill it?\n\nNathaniel Talbott <reply@reply.github.com> wrote:\n\n>@aphyr The ripple code still seems to be dependent on the VALID_OPTIONS array, so just about every Ripple test is failing now. Should this array move somewhere else, or is it going away?\n>\n>--- \n>Reply to this email directly or view it on GitHub:\n>https://github.com/seancribbs/ripple/commit/a1e40c57ddde3c138cb5f6bde6e5fa5573c6d8ff#commitcomment-710881\n>\n","html_url":"https://github.com/seancribbs/ripple/commit/a1e40c57dd#commitcomment-711411","id":711411,"path":"riak-client/lib/riak/client.rb","created_at":"2011-11-11T16:32:40Z"}}