You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Map dateTime fields (only naive with respect to time zone) into google.protobuf.Timestamp.
Map null to google.protobuf.NullValue.
Map void to google.protobuf.Empty
Maybe map unknown models to google.protobuf.Any
google.protobuf must be included somehow in the output directory (e.g. emitted by cadl-grpc alongside the user's packages) and types must be referenced using import declarations with a relative path, e.g.:
gRPC priority: 1 (IMO, this is essential)
Estimate: 5
Needs Design - should we emit the required google protobuf library components as part of the CADL spec emit or require customers to provide the google protobuf libraries themselves. Should it be configurable?
Google maintains a core protobuf library that has some shared models that are required to support some data types well: https://developers.google.com/protocol-buffers/docs/reference/google.protobuf
For example:
dateTime
fields (only naive with respect to time zone) intogoogle.protobuf.Timestamp
.null
togoogle.protobuf.NullValue
.void
togoogle.protobuf.Empty
google.protobuf.Any
google.protobuf
must be included somehow in the output directory (e.g. emitted by cadl-grpc alongside the user's packages) and types must be referenced usingimport
declarations with a relative path, e.g.:The text was updated successfully, but these errors were encountered: