Allow for namespaced models.

[gmhawash]

Our use case allows for models to be namespaced as we're taking advantage of Rails Multi-Database access. As a result, each database models are namespaced; e.g., DB1::Tenant. We also want to be able to use the parent or scope option when we access sub-associations. e.g., DB1::Tenant.has_many :certificates, hence:

expose :tenant, model_namespace: :DB1
expose :certificate, parent: :tenant, model_namespace: :DB1

This translates to:

def tenant = DB1::Tenant.find_or_initialize_by(id: params[:id])
def certificate = tenant.certificates.find_or_initialize_by(id: params[:id])

[mattpolito]

@gmhawash Thanks so much for the PR!

Before I look into this, have you tried using the model option?

It should work out like this:

expose :certificate, parent: :tenant, model: DB1::Certificate

[gmhawash]

@mattpolito the code prevents parent and model to be used at the same time.

[mattpolito]

I'd like to remedy the 'incompatible option' situation over adding and additional option for name-spacing. Let me look into that.

[gmhawash]

I would be happy to try it if you do it soonish. Thanks

[mattpolito]

I'm planning to take a look at it toward the end of the month around the holidays

[gmhawash]

Ok let me know when it is ready

…

On Dec 5, 2024, at 9:06 AM, Matt Polito ***@***.***> wrote: I'm planning to take a look at it toward the end of the month around the holidays — Reply to this email directly, view it on GitHub <#206 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAALW4UEFUZYXTLRAETBGX32ECBX7AVCNFSM6AAAAABS37WGNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRQHEZTQMJYGI>. You are receiving this because you were mentioned.

[gmhawash]

@mattpolito Hi Matt, did you get a chance to take a look at this issue?

[mattpolito]

@gmhawash I did not, was sick my entire vacation when I was going to look into it.