Closed EugenePisotsky closed 4 years ago
oh heck, you're right. I guess we need to recognize a field accessed multiple times and add additional properties to the fields object for each beyond the 1st
also, probably not the best way, but as a workaround I was thinking about using map for aliased fields in the root Query
class, something like:
Map<String, dynamic> aliasedFields = Map();
and if schemaFieldName
not equals to name
, mixin can set / get it from the aliasedFields
map
1.1.5-beta
fixes this specific issue, but there are still some serious problems in #24
Hi,
There's a problem with aliases. Query like this:
... is generated to this code:
(2 geoRoute passed to super)