AWSAppSyncClient full support for local state in gql queries (Apollo 2.5)

Do you want to request a feature or report a bug? Feature, please consider upgrading AWSAppSyncClient dependencies from Apollo 2.4 to Apollo 2.5

What is the current behavior? Local state support in Apollo 2.4 requires lots of boilerplate;

//2.4
const GET_CURRENT_THEATER = gql`
	{
    	currentTheaterId @client
	}
`;
const LIST_MOVIES = gql`
    query list($theaterId: ID!) {
        listMovies(theaterId: $theaterId) {
            id,
            name
        }
    }
`;
[...]
render() {
	return <Query query={GET_CURRENT_THEATER}>{
		queryRes => {
			const currentTheaterId = queryRes.data.currentTheaterId;
			return <Query query={LIST_MOVIES} variables={{theaterId: currentTheaterId}}>
				{this.renderMovies.bind(this)}
			</Query>
		}
	}</Query>;
}

What is the expected behavior? Apollo 2.5 brings significant improvements by supporting injection of local state directly in the query variables with the @export directive.

//2.5
const LIST_MOVIES = gql`
    query list($theaterId: ID!) {
    	currentTheaterId @client @export(as: "theaterId")
        listMovies(theaterId: $theaterId) {
            id,
            name
        }
    }
`;
[...]
render() {
	return <Query query={LIST_MOVIES}>
		{this.renderMovies.bind(this)}
	</Query>;
}

See also https://www.apollographql.com/docs/react/essentials/local-state.html#client-variables

Which versions and which environment (browser, react-native, nodejs) / OS are affected by this issue? Did this work in previous versions? aws-appsync 1.7.2

[idanlo]

Anything new with this?

[manueliglesias]

Thanks for the report, this is on our backlog, we are doing some internal testing and PoC.

I can’t give an ETA, but we’ll keep you posted in this issue