#[non_exhaustive]pub struct Options {Show 15 fields
pub verify_mode: Option<VerifyMode>,
pub overwrite_mode: Option<OverwriteMode>,
pub atime: Option<Atime>,
pub mtime: Option<Mtime>,
pub uid: Option<Uid>,
pub gid: Option<Gid>,
pub preserve_deleted_files: Option<PreserveDeletedFiles>,
pub preserve_devices: Option<PreserveDevices>,
pub posix_permissions: Option<PosixPermissions>,
pub bytes_per_second: Option<i64>,
pub task_queueing: Option<TaskQueueing>,
pub log_level: Option<LogLevel>,
pub transfer_mode: Option<TransferMode>,
pub security_descriptor_copy_flags: Option<SmbSecurityDescriptorCopyFlags>,
pub object_tags: Option<ObjectTags>,
}
Expand description
Indicates how your transfer task is configured. These options include how DataSync handles files, objects, and their associated metadata during your transfer. You also can specify how to verify data integrity, set bandwidth limits for your task, among other options.
Each option has a default value. Unless you need to, you don't have to configure any option before calling StartTaskExecution.
You also can override your task options for each task execution. For example, you might want to adjust the LogLevel
for an individual execution.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.verify_mode: Option<VerifyMode>
Specifies if and how DataSync checks the integrity of your data at the end of your transfer.
-
ONLY_FILES_TRANSFERRED
(recommended) - DataSync calculates the checksum of transferred data (including metadata) at the source location. At the end of the transfer, DataSync then compares this checksum to the checksum calculated on that data at the destination.This is the default option for Enhanced mode tasks.
We recommend this option when transferring to S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive storage classes. For more information, see Storage class considerations with Amazon S3 locations.
-
POINT_IN_TIME_CONSISTENT
- At the end of the transfer, DataSync checks the entire source and destination to verify that both locations are fully synchronized.The is the default option for Basic mode tasks and isn't currently supported with Enhanced mode tasks.
If you use a manifest, DataSync only scans and verifies what's listed in the manifest.
You can't use this option when transferring to S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive storage classes. For more information, see Storage class considerations with Amazon S3 locations.
-
NONE
- DataSync performs data integrity checks only during your transfer. Unlike other options, there's no additional verification at the end of your transfer.
overwrite_mode: Option<OverwriteMode>
Specifies whether DataSync should modify or preserve data at the destination location.
-
ALWAYS
(default) - DataSync modifies data in the destination location when source data (including metadata) has changed.If DataSync overwrites objects, you might incur additional charges for certain Amazon S3 storage classes (for example, for retrieval or early deletion). For more information, see Storage class considerations with Amazon S3 transfers.
-
NEVER
- DataSync doesn't overwrite data in the destination location even if the source data has changed. You can use this option to protect against overwriting changes made to files or objects in the destination.
atime: Option<Atime>
Specifies whether to preserve metadata indicating the last time a file was read or written to.
The behavior of Atime
isn't fully standard across platforms, so DataSync can only do this on a best-effort basis.
-
BEST_EFFORT
(default) - DataSync attempts to preserve the originalAtime
attribute on all source files (that is, the version before thePREPARING
steps of the task execution). This option is recommended. -
NONE
- IgnoresAtime
.
If Atime
is set to BEST_EFFORT
, Mtime
must be set to PRESERVE
.
If Atime
is set to NONE
, Mtime
must also be NONE
.
mtime: Option<Mtime>
Specifies whether to preserve metadata indicating the last time that a file was written to before the PREPARING
step of your task execution. This option is required when you need to run the a task more than once.
-
PRESERVE
(default) - Preserves originalMtime
, which is recommended. -
NONE
- IgnoresMtime
.
If Mtime
is set to PRESERVE
, Atime
must be set to BEST_EFFORT
.
If Mtime
is set to NONE
, Atime
must also be set to NONE
.
uid: Option<Uid>
Specifies the POSIX user ID (UID) of the file's owner.
-
INT_VALUE
(default) - Preserves the integer value of UID and group ID (GID), which is recommended. -
NONE
- Ignores UID and GID.
For more information, see Metadata copied by DataSync.
gid: Option<Gid>
Specifies the POSIX group ID (GID) of the file's owners.
-
INT_VALUE
(default) - Preserves the integer value of user ID (UID) and GID, which is recommended. -
NONE
- Ignores UID and GID.
For more information, see Understanding how DataSync handles file and object metadata.
preserve_deleted_files: Option<PreserveDeletedFiles>
Specifies whether files in the destination location that don't exist in the source should be preserved. This option can affect your Amazon S3 storage cost. If your task deletes objects, you might incur minimum storage duration charges for certain storage classes. For detailed information, see Considerations when working with Amazon S3 storage classes in DataSync.
-
PRESERVE
(default) - Ignores such destination files, which is recommended. -
REMOVE
- Deletes destination files that aren’t present in the source.
If you set this parameter to REMOVE
, you can't set TransferMode
to ALL
. When you transfer all data, DataSync doesn't scan your destination location and doesn't know what to delete.
preserve_devices: Option<PreserveDevices>
Specifies whether DataSync should preserve the metadata of block and character devices in the source location and recreate the files with that device name and metadata on the destination. DataSync copies only the name and metadata of such devices.
DataSync can't copy the actual contents of these devices because they're nonterminal and don't return an end-of-file (EOF) marker.
-
NONE
(default) - Ignores special devices (recommended). -
PRESERVE
- Preserves character and block device metadata. This option currently isn't supported for Amazon EFS.
posix_permissions: Option<PosixPermissions>
Specifies which users or groups can access a file for a specific purpose such as reading, writing, or execution of the file.
For more information, see Understanding how DataSync handles file and object metadata.
-
PRESERVE
(default) - Preserves POSIX-style permissions, which is recommended. -
NONE
- Ignores POSIX-style permissions.
DataSync can preserve extant permissions of a source location.
bytes_per_second: Option<i64>
Limits the bandwidth used by a DataSync task. For example, if you want DataSync to use a maximum of 1 MB, set this value to 1048576
(=1024*1024
).
Not applicable to Enhanced mode tasks.
task_queueing: Option<TaskQueueing>
Specifies whether your transfer tasks should be put into a queue during certain scenarios when running multiple tasks. This is ENABLED
by default.
log_level: Option<LogLevel>
Specifies the type of logs that DataSync publishes to a Amazon CloudWatch Logs log group. To specify the log group, see CloudWatchLogGroupArn.
-
BASIC
- Publishes logs with only basic information (such as transfer errors). -
TRANSFER
- Publishes logs for all files or objects that your DataSync task transfers and performs data-integrity checks on. -
OFF
- No logs are published.
transfer_mode: Option<TransferMode>
Specifies whether DataSync transfers only the data (including metadata) that differs between locations following an initial copy or transfers all data every time you run the task. If you're planning on recurring transfers, you might only want to transfer what's changed since your previous task execution.
-
CHANGED
(default) - After your initial full transfer, DataSync copies only the data and metadata that differs between the source and destination location. -
ALL
- DataSync copies everything in the source to the destination without comparing differences between the locations.
security_descriptor_copy_flags: Option<SmbSecurityDescriptorCopyFlags>
Specifies which components of the SMB security descriptor are copied from source to destination objects.
This value is only used for transfers between SMB and Amazon FSx for Windows File Server locations or between two FSx for Windows File Server locations. For more information, see Understanding how DataSync handles file and object metadata.
-
OWNER_DACL
(default) - For each copied object, DataSync copies the following metadata:-
The object owner.
-
NTFS discretionary access control lists (DACLs), which determine whether to grant access to an object.
DataSync won't copy NTFS system access control lists (SACLs) with this option.
-
-
OWNER_DACL_SACL
- For each copied object, DataSync copies the following metadata:-
The object owner.
-
NTFS discretionary access control lists (DACLs), which determine whether to grant access to an object.
-
SACLs, which are used by administrators to log attempts to access a secured object.
Copying SACLs requires granting additional permissions to the Windows user that DataSync uses to access your SMB location. For information about choosing a user with the right permissions, see required permissions for SMB, FSx for Windows File Server, or FSx for ONTAP (depending on the type of location in your transfer).
-
-
NONE
- None of the SMB security descriptor components are copied. Destination objects are owned by the user that was provided for accessing the destination location. DACLs and SACLs are set based on the destination server’s configuration.
Specifies whether you want DataSync to PRESERVE
object tags (default behavior) when transferring between object storage systems. If you want your DataSync task to ignore object tags, specify the NONE
value.
Implementations§
Source§impl Options
impl Options
Sourcepub fn verify_mode(&self) -> Option<&VerifyMode>
pub fn verify_mode(&self) -> Option<&VerifyMode>
Specifies if and how DataSync checks the integrity of your data at the end of your transfer.
-
ONLY_FILES_TRANSFERRED
(recommended) - DataSync calculates the checksum of transferred data (including metadata) at the source location. At the end of the transfer, DataSync then compares this checksum to the checksum calculated on that data at the destination.This is the default option for Enhanced mode tasks.
We recommend this option when transferring to S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive storage classes. For more information, see Storage class considerations with Amazon S3 locations.
-
POINT_IN_TIME_CONSISTENT
- At the end of the transfer, DataSync checks the entire source and destination to verify that both locations are fully synchronized.The is the default option for Basic mode tasks and isn't currently supported with Enhanced mode tasks.
If you use a manifest, DataSync only scans and verifies what's listed in the manifest.
You can't use this option when transferring to S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive storage classes. For more information, see Storage class considerations with Amazon S3 locations.
-
NONE
- DataSync performs data integrity checks only during your transfer. Unlike other options, there's no additional verification at the end of your transfer.
Sourcepub fn overwrite_mode(&self) -> Option<&OverwriteMode>
pub fn overwrite_mode(&self) -> Option<&OverwriteMode>
Specifies whether DataSync should modify or preserve data at the destination location.
-
ALWAYS
(default) - DataSync modifies data in the destination location when source data (including metadata) has changed.If DataSync overwrites objects, you might incur additional charges for certain Amazon S3 storage classes (for example, for retrieval or early deletion). For more information, see Storage class considerations with Amazon S3 transfers.
-
NEVER
- DataSync doesn't overwrite data in the destination location even if the source data has changed. You can use this option to protect against overwriting changes made to files or objects in the destination.
Sourcepub fn atime(&self) -> Option<&Atime>
pub fn atime(&self) -> Option<&Atime>
Specifies whether to preserve metadata indicating the last time a file was read or written to.
The behavior of Atime
isn't fully standard across platforms, so DataSync can only do this on a best-effort basis.
-
BEST_EFFORT
(default) - DataSync attempts to preserve the originalAtime
attribute on all source files (that is, the version before thePREPARING
steps of the task execution). This option is recommended. -
NONE
- IgnoresAtime
.
If Atime
is set to BEST_EFFORT
, Mtime
must be set to PRESERVE
.
If Atime
is set to NONE
, Mtime
must also be NONE
.
Sourcepub fn mtime(&self) -> Option<&Mtime>
pub fn mtime(&self) -> Option<&Mtime>
Specifies whether to preserve metadata indicating the last time that a file was written to before the PREPARING
step of your task execution. This option is required when you need to run the a task more than once.
-
PRESERVE
(default) - Preserves originalMtime
, which is recommended. -
NONE
- IgnoresMtime
.
If Mtime
is set to PRESERVE
, Atime
must be set to BEST_EFFORT
.
If Mtime
is set to NONE
, Atime
must also be set to NONE
.
Sourcepub fn uid(&self) -> Option<&Uid>
pub fn uid(&self) -> Option<&Uid>
Specifies the POSIX user ID (UID) of the file's owner.
-
INT_VALUE
(default) - Preserves the integer value of UID and group ID (GID), which is recommended. -
NONE
- Ignores UID and GID.
For more information, see Metadata copied by DataSync.
Sourcepub fn gid(&self) -> Option<&Gid>
pub fn gid(&self) -> Option<&Gid>
Specifies the POSIX group ID (GID) of the file's owners.
-
INT_VALUE
(default) - Preserves the integer value of user ID (UID) and GID, which is recommended. -
NONE
- Ignores UID and GID.
For more information, see Understanding how DataSync handles file and object metadata.
Sourcepub fn preserve_deleted_files(&self) -> Option<&PreserveDeletedFiles>
pub fn preserve_deleted_files(&self) -> Option<&PreserveDeletedFiles>
Specifies whether files in the destination location that don't exist in the source should be preserved. This option can affect your Amazon S3 storage cost. If your task deletes objects, you might incur minimum storage duration charges for certain storage classes. For detailed information, see Considerations when working with Amazon S3 storage classes in DataSync.
-
PRESERVE
(default) - Ignores such destination files, which is recommended. -
REMOVE
- Deletes destination files that aren’t present in the source.
If you set this parameter to REMOVE
, you can't set TransferMode
to ALL
. When you transfer all data, DataSync doesn't scan your destination location and doesn't know what to delete.
Sourcepub fn preserve_devices(&self) -> Option<&PreserveDevices>
pub fn preserve_devices(&self) -> Option<&PreserveDevices>
Specifies whether DataSync should preserve the metadata of block and character devices in the source location and recreate the files with that device name and metadata on the destination. DataSync copies only the name and metadata of such devices.
DataSync can't copy the actual contents of these devices because they're nonterminal and don't return an end-of-file (EOF) marker.
-
NONE
(default) - Ignores special devices (recommended). -
PRESERVE
- Preserves character and block device metadata. This option currently isn't supported for Amazon EFS.
Sourcepub fn posix_permissions(&self) -> Option<&PosixPermissions>
pub fn posix_permissions(&self) -> Option<&PosixPermissions>
Specifies which users or groups can access a file for a specific purpose such as reading, writing, or execution of the file.
For more information, see Understanding how DataSync handles file and object metadata.
-
PRESERVE
(default) - Preserves POSIX-style permissions, which is recommended. -
NONE
- Ignores POSIX-style permissions.
DataSync can preserve extant permissions of a source location.
Sourcepub fn bytes_per_second(&self) -> Option<i64>
pub fn bytes_per_second(&self) -> Option<i64>
Limits the bandwidth used by a DataSync task. For example, if you want DataSync to use a maximum of 1 MB, set this value to 1048576
(=1024*1024
).
Not applicable to Enhanced mode tasks.
Sourcepub fn task_queueing(&self) -> Option<&TaskQueueing>
pub fn task_queueing(&self) -> Option<&TaskQueueing>
Specifies whether your transfer tasks should be put into a queue during certain scenarios when running multiple tasks. This is ENABLED
by default.
Sourcepub fn log_level(&self) -> Option<&LogLevel>
pub fn log_level(&self) -> Option<&LogLevel>
Specifies the type of logs that DataSync publishes to a Amazon CloudWatch Logs log group. To specify the log group, see CloudWatchLogGroupArn.
-
BASIC
- Publishes logs with only basic information (such as transfer errors). -
TRANSFER
- Publishes logs for all files or objects that your DataSync task transfers and performs data-integrity checks on. -
OFF
- No logs are published.
Sourcepub fn transfer_mode(&self) -> Option<&TransferMode>
pub fn transfer_mode(&self) -> Option<&TransferMode>
Specifies whether DataSync transfers only the data (including metadata) that differs between locations following an initial copy or transfers all data every time you run the task. If you're planning on recurring transfers, you might only want to transfer what's changed since your previous task execution.
-
CHANGED
(default) - After your initial full transfer, DataSync copies only the data and metadata that differs between the source and destination location. -
ALL
- DataSync copies everything in the source to the destination without comparing differences between the locations.
Sourcepub fn security_descriptor_copy_flags(
&self,
) -> Option<&SmbSecurityDescriptorCopyFlags>
pub fn security_descriptor_copy_flags( &self, ) -> Option<&SmbSecurityDescriptorCopyFlags>
Specifies which components of the SMB security descriptor are copied from source to destination objects.
This value is only used for transfers between SMB and Amazon FSx for Windows File Server locations or between two FSx for Windows File Server locations. For more information, see Understanding how DataSync handles file and object metadata.
-
OWNER_DACL
(default) - For each copied object, DataSync copies the following metadata:-
The object owner.
-
NTFS discretionary access control lists (DACLs), which determine whether to grant access to an object.
DataSync won't copy NTFS system access control lists (SACLs) with this option.
-
-
OWNER_DACL_SACL
- For each copied object, DataSync copies the following metadata:-
The object owner.
-
NTFS discretionary access control lists (DACLs), which determine whether to grant access to an object.
-
SACLs, which are used by administrators to log attempts to access a secured object.
Copying SACLs requires granting additional permissions to the Windows user that DataSync uses to access your SMB location. For information about choosing a user with the right permissions, see required permissions for SMB, FSx for Windows File Server, or FSx for ONTAP (depending on the type of location in your transfer).
-
-
NONE
- None of the SMB security descriptor components are copied. Destination objects are owned by the user that was provided for accessing the destination location. DACLs and SACLs are set based on the destination server’s configuration.
Specifies whether you want DataSync to PRESERVE
object tags (default behavior) when transferring between object storage systems. If you want your DataSync task to ignore object tags, specify the NONE
value.
Trait Implementations§
impl StructuralPartialEq for Options
Auto Trait Implementations§
impl Freeze for Options
impl RefUnwindSafe for Options
impl Send for Options
impl Sync for Options
impl Unpin for Options
impl UnwindSafe for Options
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>
Returns self
with the
fg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.bright_black());
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>
Returns self
with the
fg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.bright_green());
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.bright_yellow());
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>
Returns self
with the
fg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.bright_magenta());
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>
Returns self
with the
fg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.bright_white());
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>
Returns self
with the
bg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.on_bright_black());
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>
Returns self
with the
bg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.on_bright_green());
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.on_bright_yellow());
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightBlue
.
§Example
println!("{}", value.on_bright_blue());
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.on_bright_magenta());
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightCyan
.
§Example
println!("{}", value.on_bright_cyan());
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.on_bright_white());
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 underline(&self) -> Painted<&T>
fn underline(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::Underline
.
§Example
println!("{}", value.underline());
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::RapidBlink
.
§Example
println!("{}", value.rapid_blink());
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);