Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a small Rails app (a blog, a task board, a bookmarks list). Requirements: generate at least TWO models with a relationship (belongs_to / has_many) and run migrations (bin/rails db:migrate); define routes with 'resources :posts' and implement the RESTful controller actions; use STRONG PARAMETERS (params.require(:post).permit(...)) before saving; render ERB VIEWS with a layout + a partial and build links with named route helpers (posts_path, post_path(@post)); and use form_with for a create/edit form (Rails adds the CSRF token automatically). Add a model VALIDATION (e.g. validates :title, presence: true) and show errors. Explain how convention-over-configuration wired the pieces by name.
Two+ models with a belongs_to/has_many relationship; migrations applied; a model validation with error display.
'resources' routes + the matching controller actions; ERB views with a layout + partial; named route helpers used instead of hardcoded paths.
Strong parameters guard mass assignment; form_with drives create/edit; the CSRF token is present (automatic).
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A RESTful CRUD resource with scaffolding ## Goal Build a small Rails app (a blog, a task board, a bookmarks list). Requirements: generate at least TWO models with a relationship (belongs_to / has_many) and run migrations (bin/rails db:migrate); define routes with 'resources :posts' and implement the RESTful controller actions; use STRONG PARAMETERS (params.require(:post).permit(...)) before saving; render ERB VIEWS with a layout + a partial and build links with named route helpers (posts_path, post_path(@post)); and use form_with for a create/edit form (Rails adds the CSRF token automatically). Add a model VALIDATION (e.g. validates :title, presence: true) and show errors. Explain how convention-over-configuration wired the pieces by name. ## Acceptance criteria - [ ] Models & migrations: Two+ models with a belongs_to/has_many relationship; migrations applied; a model validation with error display. - [ ] RESTful MVC: 'resources' routes + the matching controller actions; ERB views with a layout + partial; named route helpers used instead of hardcoded paths. - [ ] Strong params & forms: Strong parameters guard mass assignment; form_with drives create/edit; the CSRF token is present (automatic). ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.