Releases: utrack/clay
v3.2.0
v3.1.0
v3.0.1
v3.0.0
Now compatible with the new generator google.golang.org/protobuf.
Read more about this migration here: https://blog.golang.org/protobuf-apiv2.
v2.4.9
v2.4.7
This release adds automatic test file generation for generated implementation stubs.
Enabled by default; you can disable it via plugin flag tests=false
.
Changelog
c0216bd #85: use upside deferring after template generation
93af5eb Merge pull request #82 from wish-master/to_merge
d57b4ad Merge pull request #86 from wish-master/85
2e2f12c Merge remote-tracking branch 'upstream/master' into to_merge
ab3b393 PR-82: add flag to make unit test generation optional
41e07dc PR-82: getImplTemplate refactoring
329f0a9 PR-82: missing required package issue fix
e617103 add unit test files generation support
08d054b cleaned up generated tests in /integration
85d135b fixed goPkg restoration for getServiceImpl
ee1a3dc fixed implementation generation for imported RequestTypes
1dcfad2 handler: varName escapes '!'
v2.4.6
Changelog
753a886 Merge remote-tracking branch 'origin/develop'
3293577 Merge remote-tracking branch 'origin/master' into develop
915222f go mod tidy
a84ed07 goreleaser: fixed path manifest to main
b71f9ec [email protected]
0bca175 integration: removed test for [email protected]
2c9a7e3 swagger: temporarily disabled grpc-gateway DefaultErrors
v2.4.4
v2.2.0
-
Generated
ServiceDesc
now supports options passed viadesc.Apply(opts)
and implementstransport.ConfigurableServiceDesc
-
Now executing gRPC middlewares for HTTP calls
For execution, pass your interceptor viadesc.Apply(transport.WithUnaryInterceptor(ic))
clay/server
does that automatically when usingWithGRPCUnaryMiddlewares()
option.
v2.1.1
- Integration tests do not depend on local protoc-gen-goclay anymore
(#28) - Server can send custom response headers and HTTPClient users can read them (#27)
- Clients can use
grpc.Header()
option to retrieve response headers when
using generated HTTP client. - Server can use
grpc.SetHeader
/grpc.SetTrailer
in handlers to add custom
response headers and trailers. - Headers added via
metadata.AppendToOutgoingContext()
are passed
through as well.
- Clients can use
- Generated HTTPClient actually uses a given context now.