dynamic type

[jamesdixon]

Hi there,

I can see that it's possible to change the type dynamically by passing in a configuration to the serializer itself. Is this possible with relationships?

My use case is that I have a campaign model that has a relationship recipients. These recipients can be of type staff or customer.

Is this possible with the current implementation?

Thanks!

[danivek]

Hi,

Dynamic relationships are not currently possible. But I don't see any particular problems of implementing it.

[jamesdixon]

@danivek thanks. I'll submit a PR for this as soon as I get some time. Cheers

[jamesdixon]

@danivek oh wow, just saw that you had submitted a PR for this. Thanks!

[danivek]

@jamesdixon 😉. Can you give it a try and give me a feedback ? Thanks

[jamesdixon]

Will do!

…

On Apr 24, 2018, 3:53 PM -0600, Kévin Danielo ***@***.***>, wrote: @jamesdixon 😉. Can you give it a try and give me a feedback ? Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[jamesdixon]

@danivek sorry for the delay on testing this!

Is it possible to allow the function access to the entire record? Unfortunately, the id doesn't give me enough information to set the type dynamically.

For example, my campaign record has a type field, which can be either staff or customer. That field is what I'd like to use in order to set the type property on the response.

Thanks!

[jamesdixon]

@danivek wanted to see if you had any thoughts on the above? Thank you!

[danivek]

@jamesdixon you’re right ! I will change this to allow the entire record to be passed to the type resolver function.

Thank you for your feedback !

[jamesdixon]

Thanks, @danivek! Much appreciated 👍

[danivek]

Now the type resolver function has 2 arguments function(relationshipData, data) { ... }
Can you give it a try ?

Thanks @jamesdixon

[jamesdixon]

works beautifully! thx @danivek