flamerohr

wow, I wish I knew earlier that I could do thunk.withExtraArgument(apolloClient) and my reducers will look like this function getThing(dispatch, getState, apolloClient) { ... } so I didn't need to suffer all the BS of ApolloClient's HOC hell 😕

tractorcow

canEdit() doe; Permission::checkMember($member, self::EDIT_ALL) implies admin privileges

tractorcow

we just about need a new tag after every breaking change

zippy

@tractorcow should the master composer.json just use the deps like how travis is setup atm?

zippy

because you go there and it says build is passing, but it's not really right based on the current composer.json

unclecheese

what's wrong with Apollo(Apollo(Apollo(Apollo(Apollo(t)))))?

flamerohr

@zippy the trouble is we don't really want the composer.json to use dev-master as dependencies, as that would affect the users using the alpha builds if you're using dev-master then yup, add the dependencies like how travis is setup

zippy

@flamerohr understand, but for the release process maybe the composer.json is updated with current releases for those dependencies at the time perhaps as part of the build process?