Creating Long-Lived Web Apps with Ruby on Rails/

...

Use Nested Routes Strategically

Learn more about the strategic implementation of nested routes.

We'll cover the following...

Create subresources judiciously

The Rails Routing Guide says, “Resources should never be nested more than [one] level deep.” This is for a good reason, as it starts to blur the lines about what resource is being manipulated, and it creates highly complex route helpers like manufacturer_widget_order_url that take several parameters. There are three main reasons to consider a nested route:

Subresource ownership
Namespacing
Organizing content pages

Create subresources judiciously

A subresource is something properly owned by a parent resource. Using our widget ...

Prologue

Getting Started

The Rails Application Architecture

Start Our App Off Right

Business Logic

Routes and URLs

HTML Templates

Helpers

CSS

Minimize JavaScript

Carefully Manage the JavaScript We Need

Testing the View

Models I

The Database

Build an E-learning Website with Ruby-on-Rails and PostgreSQL

Business Logic Code is a Seam

Models II

End-to-End Testing

Controllers

Jobs

Other Boundary Classes

Authentication and Authorization beyond Rails

Create a Bill Split Application Using Ruby on Rails

API Endpoints

Sustainable Process and Workflows

Operations

Conclusion

Appendices

Use Nested Routes Strategically

Create subresources judiciously