Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cwgo init always return error could not find field matching protoSearch #38

Closed
rogerogers opened this issue Feb 24, 2023 · 0 comments · Fixed by #39
Closed

cwgo init always return error could not find field matching protoSearch #38

rogerogers opened this issue Feb 24, 2023 · 0 comments · Fixed by #39

Comments

@rogerogers
Copy link
Collaborator

rogerogers commented Feb 24, 2023

Describe the bug

cwgo init always return error could not find field matching protoSearch

A clear and concise description of what the bug is.

To Reproduce

syntax = "proto3";

package biz.hello;

// The greeting service definition.
option go_package = "biz/hello";

message Request {
  string message = 1;
}

message Response {
  string message = 1;
}

service Echo {
  rpc Echo (Request) returns (Response) {}
}
➜ cwgo init
? Select generate type server
? Select service type RPC
? Please input service name hello
? Please input module hello
? Please input idlpath idl/hello.proto
? Please input proto search path if exists, space as separator idl
2023/02/24 17:15:52.190868 cwgo.go:41: [Error] could not find field matching protoSearch

cwgo server works fine.

➜ cwgo server -service=hello -type RPC -idl=idl/hello.proto -module hello -I idl
go: creating new go.mod: module hello
go: to add module requirements and sums:
	go mod tidy

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots
image

If applicable, add screenshots to help explain your problem.

Kitex version:
image

Please provide the version of Kitex you are using.

Environment:

The output of go env.

Additional context

Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

1 participant