Add new package bindings option (#169)

Add new package bindings option This commit adds list of packages for which genqlient should automatically generate bindings; it's equivalent to adding all the exported types in the package to `bindings` explicitly. This can be useful when you're both a client and a server of the same schema and want to share types. We don't recommend doing things that way, but the feature isn't too invasive and may be useful for other purposes. Co-authored-by: Ben Kraft <[email protected]>
2022-06-17 11:42:49 -07:00
parent 1f44dc6db3
commit 093054ef32
5 changed files with 127 additions and 2 deletions
@@ -40,6 +40,7 @@ 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.