public static final class CreateMembershipRequest.Builder extends GeneratedMessageV3.Builder<CreateMembershipRequest.Builder> implements CreateMembershipRequestOrBuilder
Protobuf type google.chat.v1.CreateMembershipRequest
Inherited Members
com.google.protobuf.GeneratedMessageV3.Builder.getUnknownFieldSetBuilder()
com.google.protobuf.GeneratedMessageV3.Builder.internalGetMapFieldReflection(int)
com.google.protobuf.GeneratedMessageV3.Builder.internalGetMutableMapFieldReflection(int)
com.google.protobuf.GeneratedMessageV3.Builder.mergeUnknownLengthDelimitedField(int,com.google.protobuf.ByteString)
com.google.protobuf.GeneratedMessageV3.Builder.mergeUnknownVarintField(int,int)
com.google.protobuf.GeneratedMessageV3.Builder.parseUnknownField(com.google.protobuf.CodedInputStream,com.google.protobuf.ExtensionRegistryLite,int)
com.google.protobuf.GeneratedMessageV3.Builder.setUnknownFieldSetBuilder(com.google.protobuf.UnknownFieldSet.Builder)
Static Methods
getDescriptor()
public static final Descriptors.Descriptor getDescriptor()
Methods
addRepeatedField(Descriptors.FieldDescriptor field, Object value)
public CreateMembershipRequest.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)
Overrides
build()
public CreateMembershipRequest build()
buildPartial()
public CreateMembershipRequest buildPartial()
clear()
public CreateMembershipRequest.Builder clear()
Overrides
clearField(Descriptors.FieldDescriptor field)
public CreateMembershipRequest.Builder clearField(Descriptors.FieldDescriptor field)
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];
clearOneof(Descriptors.OneofDescriptor oneof)
public CreateMembershipRequest.Builder clearOneof(Descriptors.OneofDescriptor oneof)
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) = { ... }
clone()
public CreateMembershipRequest.Builder clone()
Overrides
getDefaultInstanceForType()
public CreateMembershipRequest getDefaultInstanceForType()
getDescriptorForType()
public Descriptors.Descriptor getDescriptorForType()
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];
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];
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];
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 |
|---|
| Type | Description |
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 |
|---|
| Type | Description |
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 |
|---|
| Type | Description |
boolean | Whether the membership field is set.
|
internalGetFieldAccessorTable()
protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
Overrides
isInitialized()
public final boolean isInitialized()
Overrides
mergeFrom(CreateMembershipRequest other)
public CreateMembershipRequest.Builder mergeFrom(CreateMembershipRequest other)
public CreateMembershipRequest.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
Overrides
mergeFrom(Message other)
public CreateMembershipRequest.Builder mergeFrom(Message other)
| Parameter |
|---|
| Name | Description |
other | Message
|
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];
mergeUnknownFields(UnknownFieldSet unknownFields)
public final CreateMembershipRequest.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
Overrides
setField(Descriptors.FieldDescriptor field, Object value)
public CreateMembershipRequest.Builder setField(Descriptors.FieldDescriptor field, Object value)
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];
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];
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 |
|---|
| Name | Description |
value | String
The parent to set.
|
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 |
|---|
| Name | Description |
value | ByteString
The bytes for parent to set.
|
setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
public CreateMembershipRequest.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
Overrides
setUnknownFields(UnknownFieldSet unknownFields)
public final CreateMembershipRequest.Builder setUnknownFields(UnknownFieldSet unknownFields)
Overrides
