Cannot find the definition of MessageVerifier #469
Labels
documentation
Indicates a need for improvements or additions to documentation
good first issue
Indicates a good issue for first-time contributors
help wanted
Indicates that a maintainer wants help on an issue or pull request
Software versions
go version go1.22.6 darwin/arm64
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/UserDir/Library/Caches/go-build'
GOENV='/UserDir/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/UserDir/go/pkg/mod'
GONOPROXY='xxxxx'
GONOSUMDB='xxxxx'
GOOS='darwin'
GOPATH='/UserDir/go'
GOPRIVATE='xxxxx'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/UserDir/go/pkg/mod/golang.org/[email protected]'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/UserDir/go/pkg/mod/golang.org/[email protected]/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.22.6'
GCCGO='gccgo'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/UserDir/xxxx/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/r5/23k2727j7xv5j2g3nzqk402r0000gn/T/go-build3723278093=/tmp/go-build -gno-record-gcc-switches -fno-common'
Expected behaviour
I'm writing a kafka test follow below example, from the link: https://docs.pact.io/implementation_guides/go/docs/messages#provider-producer
but I cannot find the definition of MessageVerifier and ProviderStateV3Response. I searched the pact - go project through the code - search function and found that no code defined MessageVerifier. Is there something wrong?
Actual behaviour
Please help me provide an example of testing Kafka in Golang.
Steps to reproduce
Provide a repository, gist or reproducable code snippet so that we can test the problem. You may also want to adapt one of the examples in the repository to demonstrate the problem.
Relevent log files
Please ensure you set logging to
DEBUG
and attach any relevant log files here (or link from a gist).The text was updated successfully, but these errors were encountered: