README
¶
Service Directory Documentation
Welcome to this documentation! 🎉🎉🎉 Here, we will delve into the main purpose and usage of the service directory.
1. The Service Provider: The Service Directory 📡
The
servicedirectory is the service provider of our project. It's a place where we declare the specific services that our application offers. You can think of it as the front desk 🎫 of a hotel, where guests (clients) can request specific services.
Each service provided corresponds one-to-one with the service interfaces generated under the
apidirectory'sprotofiles. This means our application can offer a wide array of services, each tailored to a specific need.
2. Protocol Compatibility and Request Handling 🎯
The
servicedirectory is also a protocol chameleon 🦎, capable of adapting to multiple protocols for service calls. In general, it allows service calls via HTTP and gRPC protocols, providing flexibility for various use-cases.
The logic in the
servicelayer mainly involves some parameter validation and request content conversion operations. Specifically, it performsreq -> bo(request to business object) conversions andbo -> rep(business object to response) operations.
By doing so, the
servicedirectory ensures that our services are robust, reliable, and adaptable to various client needs. 🚀🚀🚀
We hope this guide helps you navigate the
servicedirectory more effectively. Happy coding! 💻💻💻
Documentation
¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
var ProviderSet = wire.NewSet(NewLoginService)
Functions ¶
This section is empty.
Types ¶
type LoginService ¶
type LoginService struct {
v1.UnimplementedLoginServer
// contains filtered or unexported fields
}
func NewLoginService ¶
func NewLoginService(uc *biz.LoginUseCase) *LoginService
func (*LoginService) Login ¶
func (svc *LoginService) Login(ctx context.Context, req *v1.LoginRequest) (*v1.LoginReply, error)
Source Files