Skip to content

Document combining model_classes with prefer_conventional_models #137

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

Merged
nertzy merged 1 commit into from
Oct 14, 2026
Merged

Document combining model_classes with prefer_conventional_models #137

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
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -309,6 +309,18 @@ end

Without either setting, ambiguity keeps raising.

The preference cannot help when the real model is namespaced or otherwise not
named `table_name.classify`, such as `Catalog::Widget` for `widgets`. The two
settings combine: `model_classes` entries win for the tables they name, and the
preference handles every other ambiguous table.

```ruby
FixtureBuilder.configure do |fbuilder|
fbuilder.prefer_conventional_models = true
fbuilder.model_classes = {"widgets" => "Catalog::Widget"}
end
```

FixtureBuilder writes Rails-native metadata for every model-backed file, so
Rails can select the model without a separate fixture-class mapping. This also
supports conventionally named models, namespaced models, and the root model for
Expand Down
Loading