Skip to content

Releases: 99designs/gqlgen

v0.17.3

20 Apr 18:53
0bb262d
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.17.2...v0.17.3

v0.17.2

21 Mar 13:44
1f04d38
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.17.1...v0.17.2

v0.17.1

02 Mar 13:51
5ea50ae
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.17.0...v0.17.1

v0.17.0

02 Mar 02:24
e4be565
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.16.0...v0.17.0

v0.16.0

24 Jan 19:34
b90f975
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.15.1...v0.16.0

v0.15.1

16 Jan 17:06
7102a36
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.15.0...v0.15.1

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