Skip to content

Custom scalars, arbitrary custom derives, operation selection and bug fixes
Compare
Choose a tag to compare
@tomhoule tomhoule released this 25 Aug 12:57
0.4.0
db7ccbb
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

There are a number of breaking changes due to the new features, read the Added section attentively if you are upgrading.

Added

  • (breaking) Control over which types custom scalars deserialize to is given to the user: you now have to provide type aliases for the custom scalars in the scope of the struct under derive.
  • (breaking) Support for multi-operations documents. You can select a particular operation by naming the struct under derive after it. In case there is no match, we revert to the current behaviour: select the first operation.
  • (breaking) Support arbitrary derives on the generated response types via the response_derives option on the graphql attribute. If you were relying on the Debug impl on generated structs before, you need to add response_derives = "Debug" in the #[graphql()] attributes in your structs.

Fixed

Fixed codegen of fields with leading underscores - they were ignored, leading to wrong derived types for deserialization.
Assets 2