Searched refs:generate (Results 1 – 9 of 9) sorted by relevance
| /tonic/examples/src/gcp/ |
| H A D | README.md | 7 First, you must generate a access token via the [OAuth playground]. From here 10 button to generate an `access_token` which will show up in the HTTP response
|
| /tonic/interop/data/ |
| H A D | README.md | 14 This will generate certificates and write them to the filesystem. The effective
|
| /tonic/tonic-build/src/ |
| H A D | manual.rs | 362 fn generate(&mut self, service: &Service) { in generate() method 492 generator.generate(service); in compile()
|
| H A D | prost.rs | 222 fn generate(&mut self, service: prost_build::Service, _buf: &mut String) { in generate() method
|
| /tonic/tonic-build/ |
| H A D | README.md | 71 Then we can generate Rust code via this setup in our `build.rs`
|
| /tonic/examples/ |
| H A D | routeguide-tutorial.md | 166 Tonic can be configured to generate code as part cargo's normal build process. This is very 774 In this case, we use the [async-stream] crate to generate our outbound stream, yielding 800 - When we want editor support for the generate code and our editor does not index the generated 803 More generally, whenever we want to keep our `.proto` definitions in a central place and generate 809 1) We can keep our `.proto` definitions in a separate crate and generate our code on demand, as 824 On `cargo run`, this will generate code for the server only, and place the resulting file in
|
| /tonic/ |
| H A D | CONTRIBUTING.md | 213 crates like, for example `tonic-health`, generate their gRPC code via `codegen` 414 changelog. Tonic uses `conventional-changelog` and it's cli to generate the
|
| H A D | CHANGELOG.md | 641 * **build:** Build will now generate each service client and server into their own modules.
|
| /tonic/examples/proto/googleapis/google/pubsub/v1/ |
| H A D | pubsub.proto | 867 // If specified, Pub/Sub will generate and attach an OIDC JWT token as an
|