Class CreateMembershipRequest.Builder (0.3.0)

public static final class CreateMembershipRequest.Builder extends GeneratedMessageV3.Builder<CreateMembershipRequest.Builder> implements CreateMembershipRequestOrBuilder

Protobuf type google.chat.v1.CreateMembershipRequest

Static Methods

getDescriptor()

public static final Descriptors.Descriptor getDescriptor()
Returns
TypeDescription
Descriptor

Methods

addRepeatedField(Descriptors.FieldDescriptor field, Object value)

public CreateMembershipRequest.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)
Parameters
NameDescription
fieldFieldDescriptor
valueObject
Returns
TypeDescription
CreateMembershipRequest.Builder
Overrides

build()

public CreateMembershipRequest build()
Returns
TypeDescription
CreateMembershipRequest

buildPartial()

public CreateMembershipRequest buildPartial()
Returns
TypeDescription
CreateMembershipRequest

clear()

public CreateMembershipRequest.Builder clear()
Returns
TypeDescription
CreateMembershipRequest.Builder
Overrides

clearField(Descriptors.FieldDescriptor field)

public CreateMembershipRequest.Builder clearField(Descriptors.FieldDescriptor field)
Parameter
NameDescription
fieldFieldDescriptor
Returns
TypeDescription
CreateMembershipRequest.Builder
Overrides

clearMembership()

public CreateMembershipRequest.Builder clearMembership()

Required. The membership relation to create. The memberType field must contain a user with the user.name and user.type fields populated. The server will assign a resource name and overwrite anything specified. When a Chat app creates a membership relation for a human user, it must use the chat.memberships scope, set user.type to HUMAN, and set user.name with format users/{user}, where {user} can be the email address for the user. For users in the same Workspace organization {user} can also be the id of the person from the People API, or the id for the user in the Directory API. For example, if the People API Person profile ID for user@example.com is 123456789, you can add the user to the space by setting the membership.member.name to users/user@example.com or users/123456789. When a Chat app creates a membership relation for itself, it must use the chat.memberships.app scope, set user.type to BOT, and set user.name to users/app.

.google.chat.v1.Membership membership = 2 [(.google.api.field_behavior) = REQUIRED];

Returns
TypeDescription
CreateMembershipRequest.Builder

clearOneof(Descriptors.OneofDescriptor oneof)

public CreateMembershipRequest.Builder clearOneof(Descriptors.OneofDescriptor oneof)
Parameter
NameDescription
oneofOneofDescriptor
Returns
TypeDescription
CreateMembershipRequest.Builder
Overrides

clearParent()

public CreateMembershipRequest.Builder clearParent()

Required. The resource name of the space for which to create the membership.

Format: spaces/{space}

string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = { ... }

Returns
TypeDescription
CreateMembershipRequest.Builder

This builder for chaining.

clone()

public CreateMembershipRequest.Builder clone()
Returns
TypeDescription
CreateMembershipRequest.Builder
Overrides

getDefaultInstanceForType()

public CreateMembershipRequest getDefaultInstanceForType()
Returns
TypeDescription
CreateMembershipRequest

getDescriptorForType()

public Descriptors.Descriptor getDescriptorForType()
Returns
TypeDescription
Descriptor
Overrides

getMembership()

public Membership getMembership()

Required. The membership relation to create. The memberType field must contain a user with the user.name and user.type fields populated. The server will assign a resource name and overwrite anything specified. When a Chat app creates a membership relation for a human user, it must use the chat.memberships scope, set user.type to HUMAN, and set user.name with format users/{user}, where {user} can be the email address for the user. For users in the same Workspace organization {user} can also be the id of the person from the People API, or the id for the user in the Directory API. For example, if the People API Person profile ID for user@example.com is 123456789, you can add the user to the space by setting the membership.member.name to users/user@example.com or users/123456789. When a Chat app creates a membership relation for itself, it must use the chat.memberships.app scope, set user.type to BOT, and set user.name to users/app.

.google.chat.v1.Membership membership = 2 [(.google.api.field_behavior) = REQUIRED];

Returns
TypeDescription
Membership

The membership.

getMembershipBuilder()

public Membership.Builder getMembershipBuilder()

Required. The membership relation to create. The memberType field must contain a user with the user.name and user.type fields populated. The server will assign a resource name and overwrite anything specified. When a Chat app creates a membership relation for a human user, it must use the chat.memberships scope, set user.type to HUMAN, and set user.name with format users/{user}, where {user} can be the email address for the user. For users in the same Workspace organization {user} can also be the id of the person from the People API, or the id for the user in the Directory API. For example, if the People API Person profile ID for user@example.com is 123456789, you can add the user to the space by setting the membership.member.name to users/user@example.com or users/123456789. When a Chat app creates a membership relation for itself, it must use the chat.memberships.app scope, set user.type to BOT, and set user.name to users/app.

.google.chat.v1.Membership membership = 2 [(.google.api.field_behavior) = REQUIRED];

Returns
TypeDescription
Membership.Builder

getMembershipOrBuilder()

public MembershipOrBuilder getMembershipOrBuilder()

Required. The membership relation to create. The memberType field must contain a user with the user.name and user.type fields populated. The server will assign a resource name and overwrite anything specified. When a Chat app creates a membership relation for a human user, it must use the chat.memberships scope, set user.type to HUMAN, and set user.name with format users/{user}, where {user} can be the email address for the user. For users in the same Workspace organization {user} can also be the id of the person from the People API, or the id for the user in the Directory API. For example, if the People API Person profile ID for user@example.com is 123456789, you can add the user to the space by setting the membership.member.name to users/user@example.com or users/123456789. When a Chat app creates a membership relation for itself, it must use the chat.memberships.app scope, set user.type to BOT, and set user.name to users/app.

.google.chat.v1.Membership membership = 2 [(.google.api.field_behavior) = REQUIRED];

Returns
TypeDescription
MembershipOrBuilder

getParent()

public String getParent()

Required. The resource name of the space for which to create the membership.

Format: spaces/{space}

string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = { ... }

Returns
TypeDescription
String

The parent.

getParentBytes()

public ByteString getParentBytes()

Required. The resource name of the space for which to create the membership.

Format: spaces/{space}

string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = { ... }

Returns
TypeDescription
ByteString

The bytes for parent.

hasMembership()

public boolean hasMembership()

Required. The membership relation to create. The memberType field must contain a user with the user.name and user.type fields populated. The server will assign a resource name and overwrite anything specified. When a Chat app creates a membership relation for a human user, it must use the chat.memberships scope, set user.type to HUMAN, and set user.name with format users/{user}, where {user} can be the email address for the user. For users in the same Workspace organization {user} can also be the id of the person from the People API, or the id for the user in the Directory API. For example, if the People API Person profile ID for user@example.com is 123456789, you can add the user to the space by setting the membership.member.name to users/user@example.com or users/123456789. When a Chat app creates a membership relation for itself, it must use the chat.memberships.app scope, set user.type to BOT, and set user.name to users/app.

.google.chat.v1.Membership membership = 2 [(.google.api.field_behavior) = REQUIRED];

Returns
TypeDescription
boolean

Whether the membership field is set.

internalGetFieldAccessorTable()

protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
Returns
TypeDescription
FieldAccessorTable
Overrides

isInitialized()

public final boolean isInitialized()
Returns
TypeDescription
boolean
Overrides

mergeFrom(CreateMembershipRequest other)

public CreateMembershipRequest.Builder mergeFrom(CreateMembershipRequest other)
Parameter
NameDescription
otherCreateMembershipRequest
Returns
TypeDescription
CreateMembershipRequest.Builder

mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)

public CreateMembershipRequest.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
Parameters
NameDescription
inputCodedInputStream
extensionRegistryExtensionRegistryLite
Returns
TypeDescription
CreateMembershipRequest.Builder
Overrides
Exceptions
TypeDescription
IOException

mergeFrom(Message other)

public CreateMembershipRequest.Builder mergeFrom(Message other)
Parameter
NameDescription
otherMessage
Returns
TypeDescription
CreateMembershipRequest.Builder
Overrides

mergeMembership(Membership value)

public CreateMembershipRequest.Builder mergeMembership(Membership value)

Required. The membership relation to create. The memberType field must contain a user with the user.name and user.type fields populated. The server will assign a resource name and overwrite anything specified. When a Chat app creates a membership relation for a human user, it must use the chat.memberships scope, set user.type to HUMAN, and set user.name with format users/{user}, where {user} can be the email address for the user. For users in the same Workspace organization {user} can also be the id of the person from the People API, or the id for the user in the Directory API. For example, if the People API Person profile ID for user@example.com is 123456789, you can add the user to the space by setting the membership.member.name to users/user@example.com or users/123456789. When a Chat app creates a membership relation for itself, it must use the chat.memberships.app scope, set user.type to BOT, and set user.name to users/app.

.google.chat.v1.Membership membership = 2 [(.google.api.field_behavior) = REQUIRED];

Parameter
NameDescription
valueMembership
Returns
TypeDescription
CreateMembershipRequest.Builder

mergeUnknownFields(UnknownFieldSet unknownFields)

public final CreateMembershipRequest.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
Parameter
NameDescription
unknownFieldsUnknownFieldSet
Returns
TypeDescription
CreateMembershipRequest.Builder
Overrides

setField(Descriptors.FieldDescriptor field, Object value)

public CreateMembershipRequest.Builder setField(Descriptors.FieldDescriptor field, Object value)
Parameters
NameDescription
fieldFieldDescriptor
valueObject
Returns
TypeDescription
CreateMembershipRequest.Builder
Overrides

setMembership(Membership value)

public CreateMembershipRequest.Builder setMembership(Membership value)

Required. The membership relation to create. The memberType field must contain a user with the user.name and user.type fields populated. The server will assign a resource name and overwrite anything specified. When a Chat app creates a membership relation for a human user, it must use the chat.memberships scope, set user.type to HUMAN, and set user.name with format users/{user}, where {user} can be the email address for the user. For users in the same Workspace organization {user} can also be the id of the person from the People API, or the id for the user in the Directory API. For example, if the People API Person profile ID for user@example.com is 123456789, you can add the user to the space by setting the membership.member.name to users/user@example.com or users/123456789. When a Chat app creates a membership relation for itself, it must use the chat.memberships.app scope, set user.type to BOT, and set user.name to users/app.

.google.chat.v1.Membership membership = 2 [(.google.api.field_behavior) = REQUIRED];

Parameter
NameDescription
valueMembership
Returns
TypeDescription
CreateMembershipRequest.Builder

setMembership(Membership.Builder builderForValue)

public CreateMembershipRequest.Builder setMembership(Membership.Builder builderForValue)

Required. The membership relation to create. The memberType field must contain a user with the user.name and user.type fields populated. The server will assign a resource name and overwrite anything specified. When a Chat app creates a membership relation for a human user, it must use the chat.memberships scope, set user.type to HUMAN, and set user.name with format users/{user}, where {user} can be the email address for the user. For users in the same Workspace organization {user} can also be the id of the person from the People API, or the id for the user in the Directory API. For example, if the People API Person profile ID for user@example.com is 123456789, you can add the user to the space by setting the membership.member.name to users/user@example.com or users/123456789. When a Chat app creates a membership relation for itself, it must use the chat.memberships.app scope, set user.type to BOT, and set user.name to users/app.

.google.chat.v1.Membership membership = 2 [(.google.api.field_behavior) = REQUIRED];

Parameter
NameDescription
builderForValueMembership.Builder
Returns
TypeDescription
CreateMembershipRequest.Builder

setParent(String value)

public CreateMembershipRequest.Builder setParent(String value)

Required. The resource name of the space for which to create the membership.

Format: spaces/{space}

string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = { ... }

Parameter
NameDescription
valueString

The parent to set.

Returns
TypeDescription
CreateMembershipRequest.Builder

This builder for chaining.

setParentBytes(ByteString value)

public CreateMembershipRequest.Builder setParentBytes(ByteString value)

Required. The resource name of the space for which to create the membership.

Format: spaces/{space}

string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = { ... }

Parameter
NameDescription
valueByteString

The bytes for parent to set.

Returns
TypeDescription
CreateMembershipRequest.Builder

This builder for chaining.

setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)

public CreateMembershipRequest.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
Parameters
NameDescription
fieldFieldDescriptor
indexint
valueObject
Returns
TypeDescription
CreateMembershipRequest.Builder
Overrides

setUnknownFields(UnknownFieldSet unknownFields)

public final CreateMembershipRequest.Builder setUnknownFields(UnknownFieldSet unknownFields)
Parameter
NameDescription
unknownFieldsUnknownFieldSet
Returns
TypeDescription
CreateMembershipRequest.Builder
Overrides