Skip to content

Route Skill Improvements #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
OutlawAndy wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −5
Draft

Route Skill Improvements #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions skills/routing-patterns/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -156,20 +156,19 @@ end

## 6. Singular Resources

Use `resource` (singular) for resources where there's only one per parent:
Use `resource` (singular) instead of adding non-RESTful actions to another resource.

```ruby
resources :users do
resource :profile, only: %i[show edit update] # Only one profile per user
resource :settings, only: %i[edit update] # Only one settings per user
resource :avatar, only: %i[show update] # Only one avatar per user
resource :profile, only: %i[edit update] # Instead of edit_profile on users
resource :settings, only: %i[edit update] # Instead of edit_settings on users
end
```

**Key Points:**
- Singular resources don't have an `index` action
- URLs don't require an `:id` parameter (e.g., `/users/1/profile` not `/users/1/profiles/1`)
- Perfect for one-to-one relationships or singleton resources
- Perfect for domain concepts that have a clear owner but are not backed by their own database table (e.g., profile, settings, dashboard)

## 7. Collection and Member Routes

Expand Down