0.5.0 Introduces regression when compiling queries about gatsby-graphql-toolkit

[vladar]

Yeah, we have a prettify step to get rid of those redundant fragments. But looks like it doesn't work as expected in 0.5.0. In theory, it shouldn't break anything but I'll check it.

Thanks for reporting! 👍

[kdichev]

In my case the issue is that I have a query complexity limit from api and those fragments push the query over it

[vladar]

I think the problem is with nested ids. The prettify step basically removes duplicates of ID fragment. But in your case after we add remoteTypeName: __typename to sys field it becomes different from the ID fragment:

fragment AccordionListItemId on AccordionListItem {
  remoteTypeName: __typename
  sys {
    id
  }
}

I think in v0.5.0 this is what've changed:

fragment PageContentAccordionList__itemsCollection__0__items__0 on AccordionListItem {
  remoteTypeName: __typename
  sys {
+   remoteTypeName: __typename
    id
  }
}

Now, this fragment is not a subset of the ID fragment anymore hence not removed. Just out of curiosity - what happens if you add this to the ID fragment (not suggesting as a fix, just want to confirm my hypothesis):

fragment AccordionListItemId on AccordionListItem {
  __typename
  sys {
+   __typename
    id
  }
}

[vladar]

Should be fixed in 0.6.0