Help with best practice for naming route/view/controller/model

Okay, so here's my situation. I'm building an app where clients go to a page called **session**. This is what I want it to be called in the url, and I assume that this is therefore also what the view name should be. I don't need any resources or anything for the session itself. However, while on the session page, I want users to be able to create and update **incidents**.

So here's what I figure I need:

\- The view should be session.html.erb

\- The model should be Incident

But what about the routes and controller?

Should the controller be called Sessions or Incidents? I'm assuming Incidents, since that's what's being manipulated. What should the routes for new and update look like?

Appreciate any advice!

Leave a Comment