"Relay only supports root fields with zero or one argument" about relay HOT 8 CLOSED

This is intended, as Relay needs to understand how the argument values of the root field correspond to the response values. We've solved this by limiting the flexibility of the root field, but it is possible that we could remove this limitation.

Can you describe an example use-case where multiple arguments would be valuable?

from relay.

In my situation, I have a route with two variables (/:moduleSlug/:tutorialSlug), both required to resolve the query. I was trying to pass them to a tutorial(module: $module, tutorial: $tutorial) root query.

The INPUT_TYPE seems like it will work for now, but not ideal. Let me know if you have another idea for how this could be solved.

from relay.

How about lists and connections as root fields? That is also limited, right?

from relay.

Never mind, input objects don't work here either (Unexpected arg kind: ObjectValue)...

from relay.

@devknoll this might be a bit hacky, but have you tried getting that root query to take in a string and JSON.stringify the two variables?

@jardakotesovec Correct, connections can not be root fields at the moment. As @josephsavona mentioned, we might be able to remove these limitations

from relay.

@yuzhi So, I think in my own case, I might just change my urls to be less hierarchical (they are getting ridiculous as is...).

But lots of folks do use hierarchical urls, so it seems like a restriction worth removing, if possible.

from relay.

See #112 for more detailed explanation.

from relay.

Thanks yuzhi. I'll close this one so the discussion can move there!

from relay.