Skip to content
New issue

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

Handling of optional parameters #697

Closed
kibertoad opened this issue Jul 10, 2018 · 2 comments
Closed

Handling of optional parameters #697

kibertoad opened this issue Jul 10, 2018 · 2 comments

Comments

@kibertoad
Copy link

gRPC provides two mechanisms for handling optional parameters: Structs and FieldMasks. I couldn't find anywhere in documentation whether either of them are used for attributes that are specified as non-mandatory in Swagger. There doesn't seem to be any examples either.

Two main use-cases for this are PATCH and get?attrName=attrValue (find) operations, where you definitely want to distinguish between defined and undefined values, since searching by "name='John' && age = 0" is not the same as "name='John' && age = undefined"

@kibertoad
Copy link
Author

This #379 is related, but PATCH is only part of the story here :)

@kibertoad
Copy link
Author

Created #698 for GET and now I guess this one is redundant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant