client-preset 4.4.0 contains breaking change; config for it is undocumented & cannot be reverted

1 min read Original article ↗

Which packages are impacted by your issue?

@graphql-codegen/typescript, @graphql-codegen/client-preset

Describe the bug

#10073 made a change that removes types that are often actually used. It was released as a new default in a minor version, despite being a breaking change. On top of that, there's no documentation about it, and the config to revert it appears not to even work. It took me 30 minutes to track down why my mock data generation was broken by this release. Other people have commented on the PR that this is broken for them, but that has been missed so far and hasn't been logged as an issue. I'm surfacing the regression here.

Expected behavior

  1. No breaking changes in minor releases
  2. Breaking changes clearly documented
  3. Config to revert behaviour tested and working