Apollo-android: Code generation change 1.0.2 -> 1.1.0

Created on 23 Aug 2019  路  3Comments  路  Source: apollographql/apollo-android

When upgrading from 1.0.2 to 1.1.0, my models no longer respect the package they are declared in. They now always choose the top level. It was nice to have the separation.

compiler Bug

Most helpful comment

I have mutations and queries that live in the signup package.
Screen Shot 2019-08-23 at 9 24 47 AM

on v.1.0.2, if I wanted to import a query, I'd use

com.geneva.chat.api.signup.MyQuery

on v1.1.0, I have to use

com.geneva.chat.api.MyQuery

because the package it's in is ignored.

All 3 comments

Can you provide more details ? Ideally a small repository to reproduce or the layout of your source and generated files before and after the upgrade ?

I have mutations and queries that live in the signup package.
Screen Shot 2019-08-23 at 9 24 47 AM

on v.1.0.2, if I wanted to import a query, I'd use

com.geneva.chat.api.signup.MyQuery

on v1.1.0, I have to use

com.geneva.chat.api.MyQuery

because the package it's in is ignored.

Hm, interesting. Will check why but it seems latest changes formatting package name by schema location rather than query location.

Was this page helpful?
0 / 5 - 0 ratings