You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 10, 2019. It is now read-only.
There's no way to perform one query today. This is a pretty common use case though, so I do want to find a way to make it easier.
For apollo-link-rest, we've experimented with an @export directive that allows you to export a field name to be used as a variable further down the chain. This isn't really documented yet as we haven't officially released, but you can see it in action here. Would something like that suit your use case?
@peggyrayzis I think the @export directive working similarly between both link-state & link-rest would be valuable, that way you can make a link-state query that directly funnels into a link-rest query -- all within one call to graphql. Thoughts?
For me, @export directive looks nice. But the question is which directive to use to mark part of the query to call remote server? something like @remote? How then should it be handled at resolver level?
I'm storing locally an id of a search request and want to use it to perform a query to the remote server.
At the moment I see a solution like this:
@client
querywithApollo
componentWillReceiveProps
check for loading and received datathis.props.client
and pass the data from the local query as a variable to query data from remoteBut it doesn't look like the best solution. Any better suggestions?
The text was updated successfully, but these errors were encountered: