has_one and has_many: accept foreign_key option #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
has_one
andhas_many
macros now honorforeign_key
option, if the foreign key name should be different than guessed from class name.We've stumbled upon this when building a set of Repository classes for existing Mongoid models, which meant we had both
DealRepository
andDeal
classes, the foreign key for them used in child classes is alwaysdeal_id
, neverdeal_repository_id
.