The ability to deep filter on component objects in GraphQL and REST

[roelbeerens]

• I have created my request on the Product Board before I submitted this issue
• I have looked at all the other requests on the Product Board before I submitted this issue

Hi!

Recently I tried to limit the amount of items that are in the object of a repeatable component. I'm not 100% sure this should be done with a custom query, but it would be nice to have the ability to limit/start or use a where query on repeatable component objects in GraphQL. One-to-many relations have the ability to set a query for a nested field. Components however, do not.

If I've missed any possible solution digging through the existing issues, please let know.

Edit by @derrickmehaffy

Filtering with GraphQL and REST on the polymorphic components

[roelbeerens]

For some reason I overlooked this one, oops...

#5089

[mtrabelsi]

this is a game changer to be able to use Graphql in its full power

[derrickmehaffy]

This will likely go hand in hand with filtering via REST as well

[iserifith]

is there any plan for this in the near future

[lauriejim]

@alexandrebodin or @JabStrapi will be able to answer to this question

[alexandrebodin]

Hi, This is not planned in the near future as we see components has being embeded in en entry.

You should avoid using components if the real modeling is a relation. I know it really is practical to be able to add entries directly in the admin panel though.

@JabStrapi @Aurelsicoko I think we shoul offer support for creating relation entries directly inside the Content Manager creation view at some point so the user don't start overusing componnets instead of relations

[derrickmehaffy]

Hi, This is not planned in the near future as we see components has being embeded in en entry.

You should avoid using components if the real modeling is a relation. I know it really is practical to be able to add entries directly in the admin panel though.

@JabStrapi @Aurelsicoko I think we shoul offer support for creating relation entries directly inside the Content Manager creation view at some point so the user don't start overusing componnets instead of relations

I also 2nd this, it's something I see often

[mtrabelsi]

you can just use raw REST queries for now, it works just fine...

[exeg]

you can just use raw REST queries for now, it works just fine...

If you have complex dataset it is not fine because it limits the use of strapi

[iserifith]

you can just use raw REST queries for now, it works just fine...

what i was hoping to do was ability to deep filter on the component

something like ?component.name=something