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
I'm having the same issue. The only workaround is to add another instance of the ContractorResource, per this example. I.e. you'd have to add:
module Mm
class ContractorResource < ::ContractorResource
end
end
This is really unfortunate for pretty clear reasons, e.g. you can have disparate functionality in these two classes. Could a possible solution be to add a resource_name option on relationships similar to the current class_name option?
Working with the master branch here as we need the serialize_to_hash back. This issue also happens, with class_name not being used.
This seems to come from JoinManager#add_source_relationship which seems to be ignoring the class_name option and thus trying to compute the class name of the resource on its own.
This appears to be a regression in 0.10.x--I don't have this issue in 0.9.12. After upgrading, I'm forced to specify the class_name on the has_one, which is a non-starter for me because it's being invoked via the parent class, and I can't pass options.
Activity
naive solution for cerebris#1120
travisofthenorth commentedon Jan 18, 2018
+1
I'm having the same issue. The only workaround is to add another instance of the
ContractorResource
, per this example. I.e. you'd have to add:This is really unfortunate for pretty clear reasons, e.g. you can have disparate functionality in these two classes. Could a possible solution be to add a
resource_name
option on relationships similar to the currentclass_name
option?simonc commentedon Sep 22, 2021
Hi there,
Working with the
master
branch here as we need theserialize_to_hash
back. This issue also happens, withclass_name
not being used.This seems to come from
JoinManager#add_source_relationship
which seems to be ignoring theclass_name
option and thus trying to compute the class name of the resource on its own.❤️
arcreative commentedon Dec 30, 2021
This appears to be a regression in 0.10.x--I don't have this issue in 0.9.12. After upgrading, I'm forced to specify the
class_name
on thehas_one
, which is a non-starter for me because it's being invoked via the parent class, and I can't pass options.