On 27 December 2015 at 21:24, fugee ohu <
fuge...@gmail.com> wrote:
> On Sunday, December 27, 2015 at 4:15:57 PM UTC-5, Colin Law wrote:
>>
>> On 27 December 2015 at 21:07, fugee ohu <
fuge...@gmail.com> wrote:
>> > yikes, i dunno how @user got instantiated, i forgot to say i'm in a
>> > view, i
>> > dunno if i'm allowed to do this in a view or not: <% if
>> > Profile.find_by_user_id(
current_user.id) %>
>>
>> You can do anything you like in a view, but what is wrong with
>> <% if current_user.profile.nil? %>
>>
>> How many times do I have to ask you not to top post?
>
> Sorry Colin, It's the goolge default When you click reply the cursor flashes
> on a blank line with quoting below, that's why i always forget but I'll try
> to remember from now on Do I have to test for nil like that I'd rather use
> find or find_by more absolutely ~ thanks (merry christmas)
It is not a matter of how you test for nil, it is a matter of how you
access the profile. You suggest using
Profile.find_by_user_id(
current_user.id) but you can just do
current_user.profile. It is the same thing but much easier to
understand. You can test for nil any way you like.
Colin