You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the same underlying problem as the #183, but I don't think the model can always reliably be inferred from scope, so I didn't want to vote it for fear it might be further dismissed, even if the underlying issue is valid and solvable.
It is possible to specify a has_many with a class_name on a parent class, which is necessary when the name of the resulting accessor does not automatically map to the correct class name for the model.
As such, it seems decent_exposure should allow parent and model to both be specified. When the above configuration is used with the current code, the parent short-cut cannot be used (even though it would seem natural), because the model method in behavior.rb fails to automatically determine the correct model name.
The text was updated successfully, but these errors were encountered:
This is the same underlying problem as the #183, but I don't think the model can always reliably be inferred from scope, so I didn't want to vote it for fear it might be further dismissed, even if the underlying issue is valid and solvable.
It is possible to specify a
has_many
with aclass_name
on a parent class, which is necessary when the name of the resulting accessor does not automatically map to the correct class name for the model.As such, it seems decent_exposure should allow
parent
andmodel
to both be specified. When the above configuration is used with the current code, theparent
short-cut cannot be used (even though it would seem natural), because themodel
method inbehavior.rb
fails to automatically determine the correct model name.The text was updated successfully, but these errors were encountered: