We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey there. I love this library thanks.
I was wondering if there's a way to do nested arguments? I've messed around a bit and don't think you can unless I'm mistaken.
For example:
where: { active: { _eq: true }, shopBilling: { active: { _eq: true } } }
Of course this works:
active_eq: true
In this case though shopBilling is a related table with an object relationship, so I was hoping you could do this:
shopBilling { active_eq: true } or shopBilling.active_eq: true but to no avail.
shopBilling { active_eq: true }
shopBilling.active_eq: true
The text was updated successfully, but these errors were encountered:
Hey @Ataraxy , Thanks for pointing it out. This is a valid usecase, I forgot to handle. I will take a look and fix it in a month or so.
In meanwhile, feel free to pick it up and raise a PR as well :)
Sorry, something went wrong.
hey got any solution for this ?
@yogeshwar607 Not yet. But a PR is welcome. Otherwise will fix it in few days
No branches or pull requests
Hey there. I love this library thanks.
I was wondering if there's a way to do nested arguments? I've messed around a bit and don't think you can unless I'm mistaken.
For example:
where: { active: { _eq: true }, shopBilling: { active: { _eq: true } } }
Of course this works:
active_eq: true
In this case though shopBilling is a related table with an object relationship, so I was hoping you could do this:
shopBilling { active_eq: true }
orshopBilling.active_eq: true
but to no avail.The text was updated successfully, but these errors were encountered: