Skip to content

Releases: 99designs/gqlgen

v0.15.0

15 Jan 02:16
99be195
Compare
Choose a tag to compare

What's Changed

New Contributors

Read more

v0.14.0

08 Sep 06:24
@lwc lwc
Compare
Choose a tag to compare

Added

  • Added a changelog :-) Following the same style as Apollo Client because that feels like it gives good thanks to the community contributors.
    By @MichaelJCompton in #1512
  • Added support for methods returning (v, ok) shaped values to support Prisma Go client.
    By @steebchen in #1449
  • Added a new API to finish an already validated config
    By @benjaminjkraft in #1387

Changed

Fixed

  • Removed a data race by copying when input fields have default values.
    By @skaji in #1456
  • v0.12.2 broke the handling of pointers to slices by calling the custom Marshal and Unmarshal functions on the entire slice. It now correctly calls the custom Marshal and Unmarshal methods for each element in the slice.
    By @ananyasaxena in #1363
  • Changes in go1.16 that mean go.mod and go.sum aren't always up to date. Now go mod tidy is run after code generation.
    By @lwc in #1501
  • Errors in resolving non-nullable arrays were not correctly bubbling up to the next nullable field.
    By @wilhelmeek in #1480
  • Fixed a potential deadlock in calling error presenters.
    By @vektah in #1399
  • Fixed collectFields not correctly respecting alias fields in fragments.
    By @vmrajas in #1341
  • Return introspection document in stable order.
  • By @nyergler in #1497

v0.13.0

21 Sep 03:55
@lwc lwc
Compare
Choose a tag to compare

Added

  • IsResolver added to FieldContext - #1316

Updated

  • BC break: User errors returned from directives & resolvers are now consistently wrapped in gqlerror.Errors internally by the runtime, which has been updated to support go 1.13 unwrapping - #1312
    • Since #1115 was merged, errors from inputs have been wrapped, but didn't support unwrapping, leading to #1291
    • With all errors now wrapped before the error presenter is called, custom error presenters that use type assertions will be broken.
    • errors.As must instead be used to assert/convert error types in custom error presenters.
    • See the updated docs on customising the error presenter and the blog post on go 1.13 errors for more details.
  • Typos & tweaks to docs - #1295, #1324

v0.12.2

18 Aug 07:41
@lwc lwc
Compare
Choose a tag to compare

Fixed

  • Fixed error during gqlgen init that was making starting a new project via the getting started guide impossible
  • Fix for selecting fragments on different types with overlapping fields - #1280 thanks @jatindevdg

Updated

  • Avoid computing field path if not needed during field errors - #1288 thanks @alexsn

v0.12.1

14 Aug 03:28
@lwc lwc
Compare
Choose a tag to compare

Fixed

  • Regenerated runtime for test server

v0.12.0

14 Aug 02:41
@lwc lwc
Compare
Choose a tag to compare

Added

  • Support for the OBJECT directive - #1117 thanks @s-ichikawa
  • "PGP" added to list of common initialisms - #1198 thanks @ddevault
  • Add input path in unmarshaling errors - #1115 thanks @bowd
  • Support for pointers in custom un/marshal functions - #1277

Updated

Fixed

  • gqlgen now works in paths containing a ~ - #1137 thanks @ddevault
  • Redundant type warning in generated code - #1163 thanks @fwojciec
  • POST transport now correctly has OperationContext - #1154 thanks @gsgalloway
  • Fix panic when tracing subscriptions - #1170 thanks @alexsn
  • [Federation] Do not require a resolver for "empty" extended types - #1121 thanks @csilvers
  • Don't point to named maps & slices - #1242
  • GET transport now correctly sets a content type - #1215 thanks @ddouglas
  • Removed a bunch of unneeded nil checks from codegen - #1243
  • Fixed potential memory leak when processing uploads - #1246 thanks @arkhvoid
  • Fixed leaking file descriptors when subscription clients hangup - #1248 thanks @sotoslammer
  • Fixed incorrect gqlparser import path - #1262 thanks @sateeshpnv
  • Load source based on default config in gqlgen gen - #1134 thanks @seriousben
  • Fixed OBJECT directive to fire when there are no field directives - #1255 thanks @s-ichikawa

Thanks to everyone who contributed to this massive release!

v0.11.3

13 Mar 00:06
Compare
Choose a tag to compare

Fixed

  • Reverted a generate time performance regression from v0.11.2

v0.11.2

05 Mar 01:11
Compare
Choose a tag to compare

Added

  • Executor is now public, so if you want to build your own handler package, or skip it in tests you can - #1050
  • Uploads now make the content type available to the resolver - #1074
  • Generated resolvers now pass golint again - #1054
  • Can now check if a function is executing within an operation context - #1051

Updated

  • Now on the latest urfav cli - #1057

Fixed

  • GenerateCode is now only called once during generation - #1079

v0.11.1

18 Feb 21:57
Compare
Choose a tag to compare

Fixed

  • Panic handlers were not being called consistently, and were falling back to defaults - #1043
  • Show a sane error message when specifying a follow-schema layout dir that does not exist - #1038

v0.11.0

17 Feb 05:00
Compare
Choose a tag to compare

As we start to approach 1.0 we are going to be breaking a few interfaces to make sure things are right. There are a number of breaking changes in this release so please read https://gqlgen.com/recipes/migration-0.11/

Added

  • We now have basic Apollo Federation support. Thanks @marwan-at-work for the implementation and everyone thats been helping to test this. Docs - #851 - #885.
  • Resolver can now be regenerated as schema changes - Docs #993

Changed

  • The original handler plackage has been replaced by one that has been broken down into pluggable transports and middleware. Docs.
  • Updated gqlparser to v2.0.1 - #1027

Fixed

  • Bad code generated with nilable self marshalers - #970
  • Several codegen bugs around interface generation - #1009 #1020
  • Better error messages - #1007
  • Added inlcudeDeprecated for enums in introspection - #1028