Weird bug with our responses

[DanaMC18]

Hey Anna,

So on our page where students respond to an exit ticket's question, we are having a weird bug. We are using .each inside our form to list all the questions for a particular exit ticket along with a field for responses.

We set up an if/else inside the .each inside the form so that if a question has been responded to, the input field disappears and the student is notified that they have responded (we are redirecting to the same page similar to how we have on our controller). However, this is answering the questions in reverse order. If someone responds in the first input field for the first question, the LAST question is what then disappears and indicates a response. It is so weird and narly.

To try and solve this I created a method on the questions controller to try and order them, but its not helping, its doing the same thing.

This is the responses controller:

def new 
        @exit_ticket = ExitTicket.find_by(id: params[:exit_ticket_id])
        @questions = Question.where(exit_ticket_id: params[:exit_ticket_id])
        @response = Response.new
    end

    def create
        @response = Response.create({
            response: params[:response], 
            exit_ticket_id: params[:exit_ticket_id], 
            question_id: params[:question_id]
            })
        @exit_ticket = ExitTicket.find(params[:exit_ticket_id])
        redirect_to new_exit_ticket_response_path(@exit_ticket)
    end

This is the new view page for responses:

<%=form_tag "/exit_tickets/#{@exit_ticket.id}/responses" do %>
  <% @questions.ordered.each do |question|%>

    <% if Response.find_by(question_id: question.id) %>
        <br>
        <%=label_tag%> <%=question.question.capitalize%>
        <%=label_tag "You responded" %>
    <% else %>
        <br>
        <%=label_tag%> <%=question.question.capitalize%>
        <br>
        <%= text_area_tag :response, nil, size: "50x5" %>
        <br>
        <%= hidden_field_tag "question_id", "#{question.id}" %>
        <%=submit_tag "Submit Response" %>
    <% end %> <!-- if/else -->

  <% end %> <!-- .each -->
<% end %> <!-- form -->

And this is the method I made for QUESTIONS to order them:

def self.ordered
    all.sort {|x,y| x.created_at <=> y.created_at}
  end

Note: Instead of sort I was trying to originally use .order, but it wasn't working at all.

If you could shed some light on how to fix this weird bug, we'd really appreciate it. In the meantime I'm going to brainstorm some other ways to do it.

[annarankin]

Hey Dana, keep in mind that all of your hidden fields are going to share
the same name - throw a binding.pry in there and check what's coming
through in params!
On Dec 20, 2015 2:37 PM, "Dana C" notifications@github.com wrote:

Hey Anna,

So on our page where students respond to an exit ticket's question, we are
having a weird bug. We are using .each inside our form to list all the
questions for a particular exit ticket along with a field for responses.

We set up an if/else inside the .each inside the form so that if a
question has been responded to, the input field disappears and the student
is notified that they have responded (we are redirecting to the same page
similar to how we have on our controller). However, this is answering the
questions in reverse order. If someone responds in the first input field
for the first question, the LAST question is what then disappears and
indicates a response. It is so weird and narly.

To try and solve this I created a method on the questions controller to
try and order them, but its not helping, its doing the same thing.

This is the responses controller:

def new
@exit_ticket = ExitTicket.find_by(id: params[:exit_ticket_id])
@Questions = Question.where(exit_ticket_id: params[:exit_ticket_id])
@response = Response.new
end

def create
    @response = Response.create({
        response: params[:response],
        exit_ticket_id: params[:exit_ticket_id],
        question_id: params[:question_id]
        })
    @exit_ticket = ExitTicket.find(params[:exit_ticket_id])
    redirect_to new_exit_ticket_response_path(@exit_ticket)
end

This is the new view page for responses:

<%=form_tag "/exit_tickets/#{@exit_ticket.id}/responses" do %>
<% @questions.ordered.each do |question|%>

<% if Response.find_by(question_id: question.id) %>
    <br>
    <%=label_tag%> <%=question.question.capitalize%>
    <%=label_tag "You responded" %>
<% else %>
    <br>
    <%=label_tag%> <%=question.question.capitalize%>
    <br>
    <%= text_area_tag :response, nil, size: "50x5" %>
    <br>
    <%= hidden_field_tag "question_id", "#{question.id}" %>
    <%=submit_tag "Submit Response" %>
<% end %> <!-- if/else -->

<% end %>
<% end %>

And this is the method I made for QUESTIONS to order them:

def self.ordered
all.sort {|x,y| x.created_at <=> y.created_at}
end

Note: Instead of sort I was trying to originally use .order, but it wasn't
working at all.

If you could shed some light on how to fix this weird bug, we'd really
appreciate it. In the meantime I'm going to brainstorm some other ways to
do it.

—
Reply to this email directly or view it on GitHub
#34.

[DanaMC18]

Thanks anna,

I tried that. But I still have no idea what the issue is. I'm thinking of
just approaching this in a totally different way. Its just a waste of two
days of work.

On Sun, Dec 20, 2015 at 2:48 PM, Anna Rankin notifications@github.com
wrote:

Hey Dana, keep in mind that all of your hidden fields are going to share
the same name - throw a binding.pry in there and check what's coming
through in params!
On Dec 20, 2015 2:37 PM, "Dana C" notifications@github.com wrote:

Hey Anna,

So on our page where students respond to an exit ticket's question, we
are
having a weird bug. We are using .each inside our form to list all the
questions for a particular exit ticket along with a field for responses.

We set up an if/else inside the .each inside the form so that if a
question has been responded to, the input field disappears and the
student
is notified that they have responded (we are redirecting to the same page
similar to how we have on our controller). However, this is answering the
questions in reverse order. If someone responds in the first input field
for the first question, the LAST question is what then disappears and
indicates a response. It is so weird and narly.

To try and solve this I created a method on the questions controller to
try and order them, but its not helping, its doing the same thing.

This is the responses controller:

def new
@exit_ticket = ExitTicket.find_by(id: params[:exit_ticket_id])
@Questions = Question.where(exit_ticket_id: params[:exit_ticket_id])
@response = Response.new
end

def create
@response = Response.create({
response: params[:response],
exit_ticket_id: params[:exit_ticket_id],
question_id: params[:question_id]
})
@exit_ticket = ExitTicket.find(params[:exit_ticket_id])
redirect_to new_exit_ticket_response_path(@exit_ticket)
end

This is the new view page for responses:

<%=form_tag "/exit_tickets/#{@exit_ticket.id}/responses" do %>
<% @questions.ordered.each do |question|%>

<% if Response.find_by(question_id: question.id) %>


<%=label_tag%> <%=question.question.capitalize%>
<%=label_tag "You responded" %>
<% else %>


<%=label_tag%> <%=question.question.capitalize%>


<%= text_area_tag :response, nil, size: "50x5" %>


<%= hidden_field_tag "question_id", "#{question.id}" %>
<%=submit_tag "Submit Response" %>
<% end %>

<% end %>
<% end %>

And this is the method I made for QUESTIONS to order them:

def self.ordered
all.sort {|x,y| x.created_at <=> y.created_at}
end

Note: Instead of sort I was trying to originally use .order, but it
wasn't
working at all.

If you could shed some light on how to fix this weird bug, we'd really
appreciate it. In the meantime I'm going to brainstorm some other ways to
do it.

—
Reply to this email directly or view it on GitHub
#34.

—
Reply to this email directly or view it on GitHub
#34 (comment)
.

[DanaMC18]

Anna. I changed the whole approach. I don't have any hidden_field_tags. And
its still starting with the last question. I'm bugging out.

On Sun, Dec 20, 2015 at 3:23 PM, Dana Czinsky danaczinsky@gmail.com wrote:

Thanks anna,

I tried that. But I still have no idea what the issue is. I'm thinking of
just approaching this in a totally different way. Its just a waste of two
days of work.

On Sun, Dec 20, 2015 at 2:48 PM, Anna Rankin notifications@github.com
wrote:

Hey Dana, keep in mind that all of your hidden fields are going to share
the same name - throw a binding.pry in there and check what's coming
through in params!
On Dec 20, 2015 2:37 PM, "Dana C" notifications@github.com wrote:

Hey Anna,

So on our page where students respond to an exit ticket's question, we
are
having a weird bug. We are using .each inside our form to list all the
questions for a particular exit ticket along with a field for responses.

We set up an if/else inside the .each inside the form so that if a
question has been responded to, the input field disappears and the
student
is notified that they have responded (we are redirecting to the same
page
similar to how we have on our controller). However, this is answering
the
questions in reverse order. If someone responds in the first input field
for the first question, the LAST question is what then disappears and
indicates a response. It is so weird and narly.

To try and solve this I created a method on the questions controller to
try and order them, but its not helping, its doing the same thing.

This is the responses controller:

def new
@exit_ticket = ExitTicket.find_by(id: params[:exit_ticket_id])
@Questions = Question.where(exit_ticket_id: params[:exit_ticket_id])
@response = Response.new
end

def create
@response = Response.create({
response: params[:response],
exit_ticket_id: params[:exit_ticket_id],
question_id: params[:question_id]
})
@exit_ticket = ExitTicket.find(params[:exit_ticket_id])
redirect_to new_exit_ticket_response_path(@exit_ticket)
end

This is the new view page for responses:

<%=form_tag "/exit_tickets/#{@exit_ticket.id}/responses" do %>
<% @questions.ordered.each do |question|%>

<% if Response.find_by(question_id: question.id) %>


<%=label_tag%> <%=question.question.capitalize%>
<%=label_tag "You responded" %>
<% else %>


<%=label_tag%> <%=question.question.capitalize%>


<%= text_area_tag :response, nil, size: "50x5" %>


<%= hidden_field_tag "question_id", "#{question.id}" %>
<%=submit_tag "Submit Response" %>
<% end %>

<% end %>
<% end %>

And this is the method I made for QUESTIONS to order them:

def self.ordered
all.sort {|x,y| x.created_at <=> y.created_at}
end

Note: Instead of sort I was trying to originally use .order, but it
wasn't
working at all.

If you could shed some light on how to fix this weird bug, we'd really
appreciate it. In the meantime I'm going to brainstorm some other ways
to
do it.

—
Reply to this email directly or view it on GitHub
#34.

—
Reply to this email directly or view it on GitHub
#34 (comment)
.

[annarankin]

Hey Dana, you're going to have to make sure the name of each hidden field
or however you identify each question is different - otherwise the last one
is the only one that's going to go through. If all of your questions have a
field called question_id, the form will take the value of the last one
and not be able to pass on all of them. Does that make sense?
On Dec 20, 2015 3:29 PM, "Dana C" notifications@github.com wrote:

Anna. I changed the whole approach. I don't have any hidden_field_tags. And
its still starting with the last question. I'm bugging out.

On Sun, Dec 20, 2015 at 3:23 PM, Dana Czinsky danaczinsky@gmail.com
wrote:

Thanks anna,

I tried that. But I still have no idea what the issue is. I'm thinking of
just approaching this in a totally different way. Its just a waste of two
days of work.

On Sun, Dec 20, 2015 at 2:48 PM, Anna Rankin notifications@github.com
wrote:

Hey Dana, keep in mind that all of your hidden fields are going to share
the same name - throw a binding.pry in there and check what's coming
through in params!
On Dec 20, 2015 2:37 PM, "Dana C" notifications@github.com wrote:

Hey Anna,

So on our page where students respond to an exit ticket's question, we
are
having a weird bug. We are using .each inside our form to list all the
questions for a particular exit ticket along with a field for
responses.

We set up an if/else inside the .each inside the form so that if a
question has been responded to, the input field disappears and the
student
is notified that they have responded (we are redirecting to the same
page
similar to how we have on our controller). However, this is answering
the
questions in reverse order. If someone responds in the first input
field
for the first question, the LAST question is what then disappears and
indicates a response. It is so weird and narly.

To try and solve this I created a method on the questions controller
to
try and order them, but its not helping, its doing the same thing.

This is the responses controller:

def new
@exit_ticket = ExitTicket.find_by(id: params[:exit_ticket_id])
@Questions = Question.where(exit_ticket_id: params[:exit_ticket_id])
@response = Response.new
end

def create
@response = Response.create({
response: params[:response],
exit_ticket_id: params[:exit_ticket_id],
question_id: params[:question_id]
})
@exit_ticket = ExitTicket.find(params[:exit_ticket_id])
redirect_to new_exit_ticket_response_path(@exit_ticket)
end

This is the new view page for responses:

<%=form_tag "/exit_tickets/#{@exit_ticket.id}/responses" do %>
<% @questions.ordered.each do |question|%>

<% if Response.find_by(question_id: question.id) %>


<%=label_tag%> <%=question.question.capitalize%>
<%=label_tag "You responded" %>
<% else %>


<%=label_tag%> <%=question.question.capitalize%>


<%= text_area_tag :response, nil, size: "50x5" %>


<%= hidden_field_tag "question_id", "#{question.id}" %>
<%=submit_tag "Submit Response" %>
<% end %>

<% end %>
<% end %>

And this is the method I made for QUESTIONS to order them:

def self.ordered
all.sort {|x,y| x.created_at <=> y.created_at}
end

Note: Instead of sort I was trying to originally use .order, but it
wasn't
working at all.

If you could shed some light on how to fix this weird bug, we'd really
appreciate it. In the meantime I'm going to brainstorm some other ways
to
do it.

—
Reply to this email directly or view it on GitHub
#34.

—
Reply to this email directly or view it on GitHub
<
#34 (comment)

.

—
Reply to this email directly or view it on GitHub
#34 (comment)
.