Skip to content
New issue

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

Deep filtering returns no results #9636

Closed
3 tasks done
gkielwasser opened this issue Nov 9, 2021 · 3 comments
Closed
3 tasks done

Deep filtering returns no results #9636

gkielwasser opened this issue Nov 9, 2021 · 3 comments

Comments

@gkielwasser
Copy link
Contributor

Preflight Checklist

Describe the Bug

Both deep filtering syntax doesn't work anymore in v9.0.0. An empty translations array is returned even if entries should match.

GET &deep[translations][_filter][languages_code][_eq]=fr-CH

Results:
data: { translations : [ ] }

and

GET &deep={ "translations": { "_filter":  { "languages_code": {"_eq": "fr-CH" }  } } }

Results:
data: { translations : [ ] }

To Reproduce

Try to filter a collection that has the default relational translations applied.

Errors Shown

No response

What version of Directus are you using?

9.0.0

What version of Node.js are you using?

16.13.0

What database are you using?

Postgres

What browser are you using?

Chrome

What operating system are you using?

Windows_NT 10.0.19042

How are you deploying Directus?

locally

@joselcvarela
Copy link
Member

Hello @gkielwasser
It seems a duplicate of #9578
But you already have commented there, so why did you open this?
Is this different in any way from the other one?

@gkielwasser
Copy link
Contributor Author

Hello @gkielwasser It seems a duplicate of #9578 But you already have commented there, so why did you open this? Is this different in any way from the other one?

Hello @joselcvarela,

I thought it would be related but talking with @kwiatkk1 it seems not.

My ticket describe a bug using one of the default 2 deep filtering syntax exposed in the documentation.

The other ticket, from what I have understood seems to describe a deep filtering using a syntax where "_filter" and "translations" field is swapped from what it should be according to the documentation. I'm still not so sure I have understood well, but I let the author clarify that again.

@Oreilles
Copy link
Contributor

Closing as it is indeed a duplicate of #9578

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants