MONGOID-5563 Code Docs: Correctly use Mongoid::Association::Relatable instead of Mongoid::Association #5547
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.
This PR is code-doc changes only, it does not change any logic
Mongoid::Association
is poorly named. It is actually a mixin included in theMongoid::Document
class, which makes a document capable of being associated. (Mongoid::Associable
would be a far better name, as the general practice is for mixins to end in-able
suffix.)The association metadata classes like
HasOne
,EmbedsMany
, etc. do not inherit fromMongoid::Association
. Instead, theseinclude Mongoid::Association::Relatable
mixin as their common base.Therefore, where docs currently reference type
Association
(i.e. metadata) it is incorrect, we should replace it withMongoid::Association::Relatable
.