Ruby on Rails

On 16 June 2015 at 19:36, Elizabeth McGurty <emcgurty2@gmail.com> wrote:
> I think that it is a Rails issue. Scott writes: "Oh please, let's not turn
> the simplest of bugs into a debate on gender politics. " The developer was
> not aware that gender name could be null. And we are all okay with that....
> Seems to me a serious disconnect. This developer perhaps on a very large
> project where data requirements are not shared well. Whether is it gender
> or some other sensitive matter, it would be really cool to see some tie in
> data presentation.

As I mentioned before it was not the gender_name that was nil, it was
that there was no gender object associated with the user. The
developer did not understand the error message was caused by this and
was apparently happy with the solution to only display the gender name
if there was an associated gender. Otherwise it seems he was
perfectly happy with no specified gender. I cannot understand why
this is causing you issues.

Colin

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLshJ9tDQGhaQvwQeFT2u4sihF9XjSXoLB8baM4RWvJqHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.