We recently introduced ConnectRPC as a replacement for gRPC in our codebase. However, remnants of the gRPC library still exist in our code. For example, we are currently utilizing the gRPC error detail library to verify error details.
To streamline our codebase and reduce unnecessary dependencies, we should consider removing all remnants of the gRPC library. This could involve creating our custom error detail type or referencing ConnectRPC error types to replace the gRPC error detail library.
Description:
We recently introduced ConnectRPC as a replacement for gRPC in our codebase. However, remnants of the gRPC library still exist in our code. For example, we are currently utilizing the gRPC error detail library to verify error details.
To streamline our codebase and reduce unnecessary dependencies, we should consider removing all remnants of the gRPC library. This could involve creating our custom error detail type or referencing ConnectRPC error types to replace the gRPC error detail library.
https://github.com/yorkie-team/yorkie/blob/b494fa2d02c17e229ad3fc5cebaa7ea33231077a/cmd/yorkie/project/create.go#L61-L73
Why:
Removing the gRPC dependency will not only simplify the codebase but also make the project lighter and more efficient.