#[non_exhaustive]pub struct AdminCreateUserInputBuilder { /* private fields */ }
Expand description
A builder for AdminCreateUserInput
.
Implementations§
Source§impl AdminCreateUserInputBuilder
impl AdminCreateUserInputBuilder
Sourcepub fn user_pool_id(self, input: impl Into<String>) -> Self
pub fn user_pool_id(self, input: impl Into<String>) -> Self
The ID of the user pool where you want to create a user.
This field is required.Sourcepub fn set_user_pool_id(self, input: Option<String>) -> Self
pub fn set_user_pool_id(self, input: Option<String>) -> Self
The ID of the user pool where you want to create a user.
Sourcepub fn get_user_pool_id(&self) -> &Option<String>
pub fn get_user_pool_id(&self) -> &Option<String>
The ID of the user pool where you want to create a user.
Sourcepub fn username(self, input: impl Into<String>) -> Self
pub fn username(self, input: impl Into<String>) -> Self
The value that you want to set as the username sign-in attribute. The following conditions apply to the username parameter.
-
The username can't be a duplicate of another username in the same user pool.
-
You can't change the value of a username after you create it.
-
You can only provide a value if usernames are a valid sign-in attribute for your user pool. If your user pool only supports phone numbers or email addresses as sign-in attributes, Amazon Cognito automatically generates a username value. For more information, see Customizing sign-in attributes.
Sourcepub fn set_username(self, input: Option<String>) -> Self
pub fn set_username(self, input: Option<String>) -> Self
The value that you want to set as the username sign-in attribute. The following conditions apply to the username parameter.
-
The username can't be a duplicate of another username in the same user pool.
-
You can't change the value of a username after you create it.
-
You can only provide a value if usernames are a valid sign-in attribute for your user pool. If your user pool only supports phone numbers or email addresses as sign-in attributes, Amazon Cognito automatically generates a username value. For more information, see Customizing sign-in attributes.
Sourcepub fn get_username(&self) -> &Option<String>
pub fn get_username(&self) -> &Option<String>
The value that you want to set as the username sign-in attribute. The following conditions apply to the username parameter.
-
The username can't be a duplicate of another username in the same user pool.
-
You can't change the value of a username after you create it.
-
You can only provide a value if usernames are a valid sign-in attribute for your user pool. If your user pool only supports phone numbers or email addresses as sign-in attributes, Amazon Cognito automatically generates a username value. For more information, see Customizing sign-in attributes.
Sourcepub fn user_attributes(self, input: AttributeType) -> Self
pub fn user_attributes(self, input: AttributeType) -> Self
Appends an item to user_attributes
.
To override the contents of this collection use set_user_attributes
.
An array of name-value pairs that contain user attributes and attribute values to be set for the user to be created. You can create a user without specifying any attributes other than Username
. However, any attributes that you specify as required (when creating a user pool or in the Attributes tab of the console) either you should supply (in your call to AdminCreateUser
) or the user should supply (when they sign up in response to your welcome message).
For custom attributes, you must prepend the custom:
prefix to the attribute name.
To send a message inviting the user to sign up, you must specify the user's email address or phone number. You can do this in your call to AdminCreateUser or in the Users tab of the Amazon Cognito console for managing your user pools.
You must also provide an email address or phone number when you expect the user to do passwordless sign-in with an email or SMS OTP. These attributes must be provided when passwordless options are the only available, or when you don't submit a TemporaryPassword
.
In your AdminCreateUser
request, you can set the email_verified
and phone_number_verified
attributes to true
. The following conditions apply:
-
The email address where you want the user to receive their confirmation code and username. You must provide a value for
email
when you want to setemail_verified
totrue
, or if you setEMAIL
in theDesiredDeliveryMediums
parameter. - phone_number
-
The phone number where you want the user to receive their confirmation code and username. You must provide a value for
phone_number
when you want to setphone_number_verified
totrue
, or if you setSMS
in theDesiredDeliveryMediums
parameter.
Sourcepub fn set_user_attributes(self, input: Option<Vec<AttributeType>>) -> Self
pub fn set_user_attributes(self, input: Option<Vec<AttributeType>>) -> Self
An array of name-value pairs that contain user attributes and attribute values to be set for the user to be created. You can create a user without specifying any attributes other than Username
. However, any attributes that you specify as required (when creating a user pool or in the Attributes tab of the console) either you should supply (in your call to AdminCreateUser
) or the user should supply (when they sign up in response to your welcome message).
For custom attributes, you must prepend the custom:
prefix to the attribute name.
To send a message inviting the user to sign up, you must specify the user's email address or phone number. You can do this in your call to AdminCreateUser or in the Users tab of the Amazon Cognito console for managing your user pools.
You must also provide an email address or phone number when you expect the user to do passwordless sign-in with an email or SMS OTP. These attributes must be provided when passwordless options are the only available, or when you don't submit a TemporaryPassword
.
In your AdminCreateUser
request, you can set the email_verified
and phone_number_verified
attributes to true
. The following conditions apply:
-
The email address where you want the user to receive their confirmation code and username. You must provide a value for
email
when you want to setemail_verified
totrue
, or if you setEMAIL
in theDesiredDeliveryMediums
parameter. - phone_number
-
The phone number where you want the user to receive their confirmation code and username. You must provide a value for
phone_number
when you want to setphone_number_verified
totrue
, or if you setSMS
in theDesiredDeliveryMediums
parameter.
Sourcepub fn get_user_attributes(&self) -> &Option<Vec<AttributeType>>
pub fn get_user_attributes(&self) -> &Option<Vec<AttributeType>>
An array of name-value pairs that contain user attributes and attribute values to be set for the user to be created. You can create a user without specifying any attributes other than Username
. However, any attributes that you specify as required (when creating a user pool or in the Attributes tab of the console) either you should supply (in your call to AdminCreateUser
) or the user should supply (when they sign up in response to your welcome message).
For custom attributes, you must prepend the custom:
prefix to the attribute name.
To send a message inviting the user to sign up, you must specify the user's email address or phone number. You can do this in your call to AdminCreateUser or in the Users tab of the Amazon Cognito console for managing your user pools.
You must also provide an email address or phone number when you expect the user to do passwordless sign-in with an email or SMS OTP. These attributes must be provided when passwordless options are the only available, or when you don't submit a TemporaryPassword
.
In your AdminCreateUser
request, you can set the email_verified
and phone_number_verified
attributes to true
. The following conditions apply:
-
The email address where you want the user to receive their confirmation code and username. You must provide a value for
email
when you want to setemail_verified
totrue
, or if you setEMAIL
in theDesiredDeliveryMediums
parameter. - phone_number
-
The phone number where you want the user to receive their confirmation code and username. You must provide a value for
phone_number
when you want to setphone_number_verified
totrue
, or if you setSMS
in theDesiredDeliveryMediums
parameter.
Sourcepub fn validation_data(self, input: AttributeType) -> Self
pub fn validation_data(self, input: AttributeType) -> Self
Appends an item to validation_data
.
To override the contents of this collection use set_validation_data
.
Temporary user attributes that contribute to the outcomes of your pre sign-up Lambda trigger. This set of key-value pairs are for custom validation of information that you collect from your users but don't need to retain.
Your Lambda function can analyze this additional data and act on it. Your function can automatically confirm and verify select users or perform external API operations like logging user attributes and validation data to Amazon CloudWatch Logs.
For more information about the pre sign-up Lambda trigger, see Pre sign-up Lambda trigger.
Sourcepub fn set_validation_data(self, input: Option<Vec<AttributeType>>) -> Self
pub fn set_validation_data(self, input: Option<Vec<AttributeType>>) -> Self
Temporary user attributes that contribute to the outcomes of your pre sign-up Lambda trigger. This set of key-value pairs are for custom validation of information that you collect from your users but don't need to retain.
Your Lambda function can analyze this additional data and act on it. Your function can automatically confirm and verify select users or perform external API operations like logging user attributes and validation data to Amazon CloudWatch Logs.
For more information about the pre sign-up Lambda trigger, see Pre sign-up Lambda trigger.
Sourcepub fn get_validation_data(&self) -> &Option<Vec<AttributeType>>
pub fn get_validation_data(&self) -> &Option<Vec<AttributeType>>
Temporary user attributes that contribute to the outcomes of your pre sign-up Lambda trigger. This set of key-value pairs are for custom validation of information that you collect from your users but don't need to retain.
Your Lambda function can analyze this additional data and act on it. Your function can automatically confirm and verify select users or perform external API operations like logging user attributes and validation data to Amazon CloudWatch Logs.
For more information about the pre sign-up Lambda trigger, see Pre sign-up Lambda trigger.
Sourcepub fn temporary_password(self, input: impl Into<String>) -> Self
pub fn temporary_password(self, input: impl Into<String>) -> Self
The user's temporary password. This password must conform to the password policy that you specified when you created the user pool.
The exception to the requirement for a password is when your user pool supports passwordless sign-in with email or SMS OTPs. To create a user with no password, omit this parameter or submit a blank value. You can only create a passwordless user when passwordless sign-in is available.
The temporary password is valid only once. To complete the Admin Create User flow, the user must enter the temporary password in the sign-in page, along with a new password to be used in all future sign-ins.
If you don't specify a value, Amazon Cognito generates one for you unless you have passwordless options active for your user pool.
The temporary password can only be used until the user account expiration limit that you set for your user pool. To reset the account after that time limit, you must call AdminCreateUser
again and specify RESEND
for the MessageAction
parameter.
Sourcepub fn set_temporary_password(self, input: Option<String>) -> Self
pub fn set_temporary_password(self, input: Option<String>) -> Self
The user's temporary password. This password must conform to the password policy that you specified when you created the user pool.
The exception to the requirement for a password is when your user pool supports passwordless sign-in with email or SMS OTPs. To create a user with no password, omit this parameter or submit a blank value. You can only create a passwordless user when passwordless sign-in is available.
The temporary password is valid only once. To complete the Admin Create User flow, the user must enter the temporary password in the sign-in page, along with a new password to be used in all future sign-ins.
If you don't specify a value, Amazon Cognito generates one for you unless you have passwordless options active for your user pool.
The temporary password can only be used until the user account expiration limit that you set for your user pool. To reset the account after that time limit, you must call AdminCreateUser
again and specify RESEND
for the MessageAction
parameter.
Sourcepub fn get_temporary_password(&self) -> &Option<String>
pub fn get_temporary_password(&self) -> &Option<String>
The user's temporary password. This password must conform to the password policy that you specified when you created the user pool.
The exception to the requirement for a password is when your user pool supports passwordless sign-in with email or SMS OTPs. To create a user with no password, omit this parameter or submit a blank value. You can only create a passwordless user when passwordless sign-in is available.
The temporary password is valid only once. To complete the Admin Create User flow, the user must enter the temporary password in the sign-in page, along with a new password to be used in all future sign-ins.
If you don't specify a value, Amazon Cognito generates one for you unless you have passwordless options active for your user pool.
The temporary password can only be used until the user account expiration limit that you set for your user pool. To reset the account after that time limit, you must call AdminCreateUser
again and specify RESEND
for the MessageAction
parameter.
Sourcepub fn force_alias_creation(self, input: bool) -> Self
pub fn force_alias_creation(self, input: bool) -> Self
This parameter is used only if the phone_number_verified
or email_verified
attribute is set to True
. Otherwise, it is ignored.
If this parameter is set to True
and the phone number or email address specified in the UserAttributes
parameter already exists as an alias with a different user, this request migrates the alias from the previous user to the newly-created user. The previous user will no longer be able to log in using that alias.
If this parameter is set to False
, the API throws an AliasExistsException
error if the alias already exists. The default value is False
.
Sourcepub fn set_force_alias_creation(self, input: Option<bool>) -> Self
pub fn set_force_alias_creation(self, input: Option<bool>) -> Self
This parameter is used only if the phone_number_verified
or email_verified
attribute is set to True
. Otherwise, it is ignored.
If this parameter is set to True
and the phone number or email address specified in the UserAttributes
parameter already exists as an alias with a different user, this request migrates the alias from the previous user to the newly-created user. The previous user will no longer be able to log in using that alias.
If this parameter is set to False
, the API throws an AliasExistsException
error if the alias already exists. The default value is False
.
Sourcepub fn get_force_alias_creation(&self) -> &Option<bool>
pub fn get_force_alias_creation(&self) -> &Option<bool>
This parameter is used only if the phone_number_verified
or email_verified
attribute is set to True
. Otherwise, it is ignored.
If this parameter is set to True
and the phone number or email address specified in the UserAttributes
parameter already exists as an alias with a different user, this request migrates the alias from the previous user to the newly-created user. The previous user will no longer be able to log in using that alias.
If this parameter is set to False
, the API throws an AliasExistsException
error if the alias already exists. The default value is False
.
Sourcepub fn message_action(self, input: MessageActionType) -> Self
pub fn message_action(self, input: MessageActionType) -> Self
Set to RESEND
to resend the invitation message to a user that already exists, and to reset the temporary-password duration with a new temporary password. Set to SUPPRESS
to suppress sending the message. You can specify only one value.
Sourcepub fn set_message_action(self, input: Option<MessageActionType>) -> Self
pub fn set_message_action(self, input: Option<MessageActionType>) -> Self
Set to RESEND
to resend the invitation message to a user that already exists, and to reset the temporary-password duration with a new temporary password. Set to SUPPRESS
to suppress sending the message. You can specify only one value.
Sourcepub fn get_message_action(&self) -> &Option<MessageActionType>
pub fn get_message_action(&self) -> &Option<MessageActionType>
Set to RESEND
to resend the invitation message to a user that already exists, and to reset the temporary-password duration with a new temporary password. Set to SUPPRESS
to suppress sending the message. You can specify only one value.
Sourcepub fn desired_delivery_mediums(self, input: DeliveryMediumType) -> Self
pub fn desired_delivery_mediums(self, input: DeliveryMediumType) -> Self
Appends an item to desired_delivery_mediums
.
To override the contents of this collection use set_desired_delivery_mediums
.
Specify EMAIL
if email will be used to send the welcome message. Specify SMS
if the phone number will be used. The default value is SMS
. You can specify more than one value.
Sourcepub fn set_desired_delivery_mediums(
self,
input: Option<Vec<DeliveryMediumType>>,
) -> Self
pub fn set_desired_delivery_mediums( self, input: Option<Vec<DeliveryMediumType>>, ) -> Self
Specify EMAIL
if email will be used to send the welcome message. Specify SMS
if the phone number will be used. The default value is SMS
. You can specify more than one value.
Sourcepub fn get_desired_delivery_mediums(&self) -> &Option<Vec<DeliveryMediumType>>
pub fn get_desired_delivery_mediums(&self) -> &Option<Vec<DeliveryMediumType>>
Specify EMAIL
if email will be used to send the welcome message. Specify SMS
if the phone number will be used. The default value is SMS
. You can specify more than one value.
Sourcepub fn client_metadata(self, k: impl Into<String>, v: impl Into<String>) -> Self
pub fn client_metadata(self, k: impl Into<String>, v: impl Into<String>) -> Self
Adds a key-value pair to client_metadata
.
To override the contents of this collection use set_client_metadata
.
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminCreateUser API action, Amazon Cognito invokes the function that is assigned to the pre sign-up trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a ClientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminCreateUser request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
For more information, see Using Lambda triggers in the Amazon Cognito Developer Guide.
When you use the ClientMetadata
parameter, note that Amazon Cognito won't do the following:
-
Store the
ClientMetadata
value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, theClientMetadata
parameter serves no purpose. -
Validate the
ClientMetadata
value. -
Encrypt the
ClientMetadata
value. Don't send sensitive information in this parameter.
Sourcepub fn set_client_metadata(self, input: Option<HashMap<String, String>>) -> Self
pub fn set_client_metadata(self, input: Option<HashMap<String, String>>) -> Self
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminCreateUser API action, Amazon Cognito invokes the function that is assigned to the pre sign-up trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a ClientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminCreateUser request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
For more information, see Using Lambda triggers in the Amazon Cognito Developer Guide.
When you use the ClientMetadata
parameter, note that Amazon Cognito won't do the following:
-
Store the
ClientMetadata
value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, theClientMetadata
parameter serves no purpose. -
Validate the
ClientMetadata
value. -
Encrypt the
ClientMetadata
value. Don't send sensitive information in this parameter.
Sourcepub fn get_client_metadata(&self) -> &Option<HashMap<String, String>>
pub fn get_client_metadata(&self) -> &Option<HashMap<String, String>>
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.
You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminCreateUser API action, Amazon Cognito invokes the function that is assigned to the pre sign-up trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a ClientMetadata
attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminCreateUser request. In your function code in Lambda, you can process the clientMetadata
value to enhance your workflow for your specific needs.
For more information, see Using Lambda triggers in the Amazon Cognito Developer Guide.
When you use the ClientMetadata
parameter, note that Amazon Cognito won't do the following:
-
Store the
ClientMetadata
value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, theClientMetadata
parameter serves no purpose. -
Validate the
ClientMetadata
value. -
Encrypt the
ClientMetadata
value. Don't send sensitive information in this parameter.
Sourcepub fn build(self) -> Result<AdminCreateUserInput, BuildError>
pub fn build(self) -> Result<AdminCreateUserInput, BuildError>
Consumes the builder and constructs a AdminCreateUserInput
.
Source§impl AdminCreateUserInputBuilder
impl AdminCreateUserInputBuilder
Sourcepub async fn send_with(
self,
client: &Client,
) -> Result<AdminCreateUserOutput, SdkError<AdminCreateUserError, HttpResponse>>
pub async fn send_with( self, client: &Client, ) -> Result<AdminCreateUserOutput, SdkError<AdminCreateUserError, HttpResponse>>
Sends a request with this input using the given client.
Trait Implementations§
Source§impl Clone for AdminCreateUserInputBuilder
impl Clone for AdminCreateUserInputBuilder
Source§fn clone(&self) -> AdminCreateUserInputBuilder
fn clone(&self) -> AdminCreateUserInputBuilder
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for AdminCreateUserInputBuilder
impl Debug for AdminCreateUserInputBuilder
Source§impl Default for AdminCreateUserInputBuilder
impl Default for AdminCreateUserInputBuilder
Source§fn default() -> AdminCreateUserInputBuilder
fn default() -> AdminCreateUserInputBuilder
Source§impl PartialEq for AdminCreateUserInputBuilder
impl PartialEq for AdminCreateUserInputBuilder
Source§fn eq(&self, other: &AdminCreateUserInputBuilder) -> bool
fn eq(&self, other: &AdminCreateUserInputBuilder) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for AdminCreateUserInputBuilder
Auto Trait Implementations§
impl Freeze for AdminCreateUserInputBuilder
impl RefUnwindSafe for AdminCreateUserInputBuilder
impl Send for AdminCreateUserInputBuilder
impl Sync for AdminCreateUserInputBuilder
impl Unpin for AdminCreateUserInputBuilder
impl UnwindSafe for AdminCreateUserInputBuilder
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);