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

Optional fields are filled with default empty values #76

Open
ulshv opened this issue Nov 23, 2021 · 3 comments
Open

Optional fields are filled with default empty values #76

ulshv opened this issue Nov 23, 2021 · 3 comments

Comments

@ulshv
Copy link

ulshv commented Nov 23, 2021

Let's say we have the following schema:

message UpdatePostPayload {
    optional string title = 1;
    optional string content = 2;
    optional string cover = 3;
}

The request message form will include this fields and when it's sent and parsed on the server this fields will exists with default empty values (empty strings in this example). It would be nice to be able to have checkbox or someting to specify which optional fields should be used or not. So when optional field doesn't have any value and it's unchecked (i.e. "don't use this field") - we will not get this empty values on the server.

@toly-pepperstone
Copy link

Having this issue as well!

@Ferum-bot
Copy link

Having this issue as well))))

@josuerzslzr
Copy link

Same issue here.
Is there any way to omit a field from the payload instead of sending empty string?

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

4 participants