@paltman take a look at each of the following commits:
c1a47611031bb584cec49c4a08c370f8947eb572 introduces the apollo object
930b563b3d3414ce161b55cba71c54dfcf7320e5 refactors the query to use name matching (so we can access the data via whatever name we want (e.g. libraryTree), rather than the name of the response from GraphQL
a9f0ad82caa2a76442f113468d2d691dcc3dcbe3 uses that libraryTree from the component data (rather than the $apolloData handler which is still useful for getting at loading information)
b255931f4e37850988deb20827b39cb17e94191d removes the computed property and just works off of the libraryTree data prop
I'll let you decide if you wan to take this further / explore with ApolloComponent, but I think this at least answers the question of "how does vue-apollo query syntax map onto what we've been doing so far?"
@paltman take a look at each of the following commits:
apolloobjectlibraryTree), rather than the name of the response from GraphQLlibraryTreefrom the component data (rather than the$apolloDatahandler which is still useful for getting at loading information)libraryTreedata propI'll let you decide if you wan to take this further / explore with
ApolloComponent, but I think this at least answers the question of "how doesvue-apolloquery syntax map onto what we've been doing so far?"