Searched refs:generated (Results 1 – 13 of 13) sorted by relevance
| /tonic/tonic-reflection/src/ |
| H A D | lib.rs | 10 mod generated { module 51 pub use crate::generated::{ 58 pub use crate::generated::{
|
| /tonic/tonic-types/src/ |
| H A D | lib.rs | 148 mod generated { module 172 pub use crate::generated::{google_rpc::*, FILE_DESCRIPTOR_SET};
|
| /tonic/tonic-health/src/ |
| H A D | lib.rs | 18 mod generated { module 42 pub use crate::generated::{grpc_health_v1::*, FILE_DESCRIPTOR_SET};
|
| /tonic/tonic-build/ |
| H A D | README.md | 76 //.out_dir("src/google") // you can change the generated code's location 84 Then you can reference the generated Rust like this this in your code: 92 Or if you want to save the generated code in your own code base,
|
| /tonic/tests/ambiguous_methods/proto/ |
| H A D | ambiguous_methods.proto | 8 // The generated stubs can confuse drop and clone
|
| /tonic/interop/data/ |
| H A D | README.md | 4 implementation of gRPC and the Go implementation. Certificates are generated
|
| /tonic/tonic/benches-disabled/ |
| H A D | README.md | 12 2) The `thrpt` value generated by Criterion is simply a measure of bytes consumed by the target fun…
|
| /tonic/examples/ |
| H A D | routeguide-tutorial.md | 167 convenient because once we've set everything up, there is no extra step to keep the generated code 204 That's it. The generated code contains: 210 If your are curious as to where the generated files are, keep reading. The mystery will be revealed 223 - Implementing the service trait generated from our service definition. 240 Next, we need to implement the `route_guide_server::RouteGuide` trait that is generated in our buil… 241 The generated code is placed inside our target directory, in a location defined by the `OUT_DIR` 242 environment variable that is set by cargo. For our example, this means you can find the generated 247 We can use Tonic's `include_proto` macro to bring the generated code into scope: 592 case, we'll start by bringing the generated code into scope: 611 Same as in the server implementation, we start by bringing our generated code into scope. We then [all …]
|
| /tonic/tonic-types/ |
| H A D | README.md | 112 vector of standard error messages that will be generated or that was received,
|
| /tonic/ |
| H A D | CHANGELOG.md | 26 * **channel:** Re-enable TLS based on Cargo features in generated clients (#1866) 51 * **build:** Custom codecs for generated code ([#1599](https://github.com/hyperium/tonic/issues/159… 73 * `tonic_reflection::server` is updated to use the generated 457 * **build:** Add content-type for generated unimplemented service ([#441](https://github.com/hyperi… 458 * **build:** Match namespace code with other generated packages ([#472](https://github.com/hyperium… 502 * **build:** Make generated server service public ([#347](https://github.com/hyperium/tonic/issues/… 612 * **build:** Prevent duplicated client/server generated code ([#121](https://github.com/hyperium/to… 717 * **codgen:** Add default implementations for the generated serve… ([#27](https://github.com/hyperi…
|
| H A D | CONTRIBUTING.md | 185 Lines that start with `/// #` are removed when the documentation is generated. 211 When making changes to `tonic-build` that affects the generated code you will 421 Once the entries have been generated, you must edit the `CHANGELOG.md` file
|
| /tonic/tonic-types/proto/ |
| H A D | error_details.proto | 123 // generated by some common infrastructure, the error domain must be a
|
| /tonic/examples/proto/googleapis/google/pubsub/v1/ |
| H A D | pubsub.proto | 419 // (https://cloud.google.com/pubsub/docs/admin#resource_names). The generated 575 // generated name is populated in the returned Snapshot object. Note that for
|