Move changelog entry to the right version (#217)
Thanks to `git merge` being clever, this got put in `v0.5.0` even though it was added after `v0.5.0` was released. Now it's in `vNext` (perhaps soon to become `v0.5.1`).
This commit is contained in:
+2
-1
@@ -24,6 +24,8 @@ When releasing a new version:
|
||||
|
||||
### New features:
|
||||
|
||||
- You can now bind all types from a package in `genqlient.yaml` using the new `package_bindings` option.
|
||||
|
||||
### Bug fixes:
|
||||
|
||||
- Fixed non-deterministic generated code when querying graphql interfaces
|
||||
@@ -42,7 +44,6 @@ Version 0.5.0 adds several new configuration options and convenience features. N
|
||||
- genqlient can now run as a portable binary (i.e. without a local checkout of the repository or `go run`).
|
||||
- You can now enable `use_extensions` in the configuration file, to receive extensions returned by the GraphQL API server. Generated functions will return extensions as `map[string]interface{}`, if enabled.
|
||||
- You can now use `graphql.NewClientUsingGet` to create a client that uses query parameters to pass the query to the GraphQL API server.
|
||||
- You can now bind all types from a package in `genqlient.yaml` using the new `package_bindings` option.
|
||||
- In config files, `schema`, `operations`, and `generated` can now be absolute paths.
|
||||
- You can now configure how nullable types are mapped to Go types in the configuration file. Specifically, you can set `optional: pointer` to have all nullable GraphQL arguments, input fields, and output fields map to pointers.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user