ethantsien

Results 6 issues of ethantsien

the Store method Get does not return if the answer exists or not,so the non-exists id will match the empty answer

# images ![image-1](https://github.com/relxet/res/blob/master/kitex/20230905/01.png?raw=true) ![image-2](https://github.com/relxet/res/blob/master/kitex/20230905/02.png?raw=true) ![image-3](https://github.com/relxet/res/blob/master/kitex/20230905/03.png?raw=true) # hello.proto ``` syntax = "proto3"; package hello; option go_package="pb/hello"; import "google/rpc/status.proto"; import "google/protobuf/any.proto"; message helloReq { } message helloResp { google.rpc.Status status = 1;...

Is it designed this way? Is there a plan to generate a corresponding golang integer type based on the integer type in mysql?

I think ServiceContext can not import any modules of its own project except Config, so that it can play its best role. For example, as I mentioned in the title,...

stale

I want to use the original redis client initialized by gozero, because a hook has been added, and the trace is in this hook

stale

生成的代码中,logic包依赖svc包,svc包又依赖middleware包,那么由于循环依赖的问题,middleware中就根本不可能调用logic包中的代码。 我觉得不应该把middleware的实例放在ServiceContext中,而是应该让middleware依赖svc包,把ServiceContext传入middleware来初始化, handler/routes.go中应该生成这样的代码rest.Middleware{middleware.NewFooMiddleware(serverCtx).Handle},而不是现在这样rest.Middleware{serverCtx.FooMiddleware} ----------------------- 再补充个理由: 既然handler是依赖svc包的,middleware和handler有一样的行为,也应该是让middleware依赖svc,而不是svc包依赖middleware