I am inheriting an api decision in an SDK I am writing where I am required to fetch domain objects (entries) from the server like this:blogEntries = client.content_type('blog').entriesAs you can see, the setter for the content_type property here is parameterised. To implement this design my Client class has a method like this that sets the @content_type instance variable before passing it on to other objects:def content_type(content_type_uid)  @content_type = content_type_uid  // do something with @content_typeendNow elsewhere in the class when I need to fetch back the content_type I can no longer call an attr_reader method like configuration.content_type because it conflicts with the method above. Now that forces me to have a separate getter method called get_content_type which is really non-idiomatic ruby. How do I work myself out of this conflicting situation where instead of a conventional setter like content_type= I have a setter with a different signature? What kind of trade-off would make most sense?
Conflict in getter and setter method names in ruby api design
object oriented;api design;getters