Releases: zth/rescript-relay
Releases · zth/rescript-relay
4.0.0
3.5.0
3.4.0
- Add support for
@exhaustive- a directive to trigger exhaustiveness checks for unions at the GraphQL operation level. - BREAKING Drop
__typenamein inline records, since that conflicts with using@tag("__typename")in ReScript v12 and is not necessary since__typenameis set automatically via@tag.
3.3.0
- Add support for top level
@catchon fragments on unions. - Add parameter
excludedIds: array<dataId>toinvalidateRecordsByIdsto allow excluding a list of connection IDs from invalidation. - BREAKING:
operation.textandoperation.idare now nullable, which better reflects what values they can actually have in runtime. - fix bug where custom scalars would error when set to null in refetch variables.
3.1.0
This brings the Relay version to 18.2.0.
If you have enabled the feature flags in relay.config.js for aliased fragments or Relay resolvers you'll need to remove them from the config file as they are now on by default, and not removing them will cause the compiler to fail with a non super helpful error message.
- Upgrade versions:
react-relayandrelay-runtimeto18.2.0. - Add support for
Fragment.waitForFragmentData, a new API in Relay 18.2 that lets you wait for fragment data outside of React. - Experimental: Add a "non React" mode to the PPX, which makes sure only APIs that don't rely on React directly are exposed. This is intended to be a way to simplify using RescriptRelay without React. Activate by passing
-non-reactto the PPX, like"ppx-flags": [["rescript-relay/ppx", "-non-react"]].