Skip to content

Optional fields are filled with default empty values #76

@ulshv

Description

@ulshv

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions