We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It might be useful to have nested/complex messages, parts of which are specified in query.
prost-build seems to work with them well (the rust code is generated accordingly). However, actix-prost fails with
prost-build
actix-prost
thread 'main' panicked at actix-prost-build/src/request.rs:75:13: some path fields were not found: [<field names>]
Let's say we have the following protobuf:
... message Foo { // some_scary_inner_details string inner = 1; } message Bar { // some_scary_inner_details string inner = 1; } message CreateSometingRequest { Foo foo = 1; Bar bar = 2; } service SomeService { rpc CreateSomething(CreateSometingRequest) returns (Something); }
so the request message has 2 non-primitive fields.
The .yaml config:
.yaml
... http: rules: - selector: "foo.SomeService.CreateSomething" post: /service/{foo.inner}/{bar.inner}
seems relevant; not sure
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It might be useful to have nested/complex messages, parts of which are specified in query.
prost-build
seems to work with them well (the rust code is generated accordingly). However,actix-prost
fails withExample
Let's say we have the following protobuf:
so the request message has 2 non-primitive fields.
The
.yaml
config:Possible fix directions
seems relevant; not sure
The text was updated successfully, but these errors were encountered: