Databases
StackOverflow2013
Postsdbo
POroutes when nested resource and nested attribute
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POroutes when nested resource and nested attribute
    text
    copied!<p>I have a Review model which is nested resource of Publication model. Review model have accept_nested_attributes_for review_comments. I wonder how could I show delete path to delete review_commment?</p> <pre><code>&lt;% @review.review_comments.each do |review_comment| %&gt; &lt;%= link_to "delete", ???, method: :delete %&gt; &lt;% end %&gt; </code></pre> <p>review.rb</p> <pre><code>has_many :review_comments, :dependent =&gt; :destroy accepts_nested_attributes_for :review_comments, :allow_destroy =&gt; :true </code></pre> <p>review_comment.rb</p> <pre><code>belongs_to :review </code></pre> <p>publication.rb</p> <pre><code>has_many :reviews </code></pre> <p>routes.rb</p> <pre><code>resources :publications do resources :reviews end resources :review_comments </code></pre> <p>UPDATE</p> <pre><code>def create @review_comment = ReviewComment.new(params[:review_comment]) if @review_comment.save redirect_to @review_comment, notice: 'Review comment was successfully created.' .... end def destroy @review_comment = ReviewComment.find(params[:id]) @review_comment.destroy redirect_to :back, notice: "Deleted" end </code></pre> <p>UPDATE</p> <pre><code> review_comments GET /review_comments(.:format) review_comments#index POST /review_comments(.:format) review_comments#create new_review_comment GET /review_comments/new(.:format) review_comments#new edit_review_comment GET /review_comments/:id/edit(.:format) review_comments#edit review_comment GET /review_comments/:id(.:format) review_comments#show PUT /review_comments/:id(.:format) review_comments#update DELETE /review_comments/:id(.:format) review_comments#destroy </code></pre>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload