#[non_exhaustive]pub struct RuleBasedPropertiesBuilder { /* private fields */ }Expand description
A builder for RuleBasedProperties.
Implementations§
Source§impl RuleBasedPropertiesBuilder
impl RuleBasedPropertiesBuilder
Sourcepub fn rules(self, input: Rule) -> Self
pub fn rules(self, input: Rule) -> Self
Appends an item to rules.
To override the contents of this collection use set_rules.
A list of Rule objects, each of which have fields RuleName and MatchingKeys.
Sourcepub fn set_rules(self, input: Option<Vec<Rule>>) -> Self
pub fn set_rules(self, input: Option<Vec<Rule>>) -> Self
A list of Rule objects, each of which have fields RuleName and MatchingKeys.
Sourcepub fn get_rules(&self) -> &Option<Vec<Rule>>
pub fn get_rules(&self) -> &Option<Vec<Rule>>
A list of Rule objects, each of which have fields RuleName and MatchingKeys.
Sourcepub fn attribute_matching_model(self, input: AttributeMatchingModel) -> Self
pub fn attribute_matching_model(self, input: AttributeMatchingModel) -> Self
The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the attributeMatchingModel.
If you choose MANY_TO_MANY, the system can match attributes across the sub-types of an attribute type. For example, if the value of the Email field of Profile A and the value of BusinessEmail field of Profile B matches, the two profiles are matched on the Email attribute type.
If you choose ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for the Email attribute type, the system will only consider it a match if the value of the Email field of Profile A matches the value of the Email field of Profile B.
Sourcepub fn set_attribute_matching_model(
self,
input: Option<AttributeMatchingModel>,
) -> Self
pub fn set_attribute_matching_model( self, input: Option<AttributeMatchingModel>, ) -> Self
The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the attributeMatchingModel.
If you choose MANY_TO_MANY, the system can match attributes across the sub-types of an attribute type. For example, if the value of the Email field of Profile A and the value of BusinessEmail field of Profile B matches, the two profiles are matched on the Email attribute type.
If you choose ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for the Email attribute type, the system will only consider it a match if the value of the Email field of Profile A matches the value of the Email field of Profile B.
Sourcepub fn get_attribute_matching_model(&self) -> &Option<AttributeMatchingModel>
pub fn get_attribute_matching_model(&self) -> &Option<AttributeMatchingModel>
The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the attributeMatchingModel.
If you choose MANY_TO_MANY, the system can match attributes across the sub-types of an attribute type. For example, if the value of the Email field of Profile A and the value of BusinessEmail field of Profile B matches, the two profiles are matched on the Email attribute type.
If you choose ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for the Email attribute type, the system will only consider it a match if the value of the Email field of Profile A matches the value of the Email field of Profile B.
Sourcepub fn match_purpose(self, input: MatchPurpose) -> Self
pub fn match_purpose(self, input: MatchPurpose) -> Self
An indicator of whether to generate IDs and index the data or not.
If you choose IDENTIFIER_GENERATION, the process generates IDs and indexes the data.
If you choose INDEXING, the process indexes the data without generating IDs.
Sourcepub fn set_match_purpose(self, input: Option<MatchPurpose>) -> Self
pub fn set_match_purpose(self, input: Option<MatchPurpose>) -> Self
An indicator of whether to generate IDs and index the data or not.
If you choose IDENTIFIER_GENERATION, the process generates IDs and indexes the data.
If you choose INDEXING, the process indexes the data without generating IDs.
Sourcepub fn get_match_purpose(&self) -> &Option<MatchPurpose>
pub fn get_match_purpose(&self) -> &Option<MatchPurpose>
An indicator of whether to generate IDs and index the data or not.
If you choose IDENTIFIER_GENERATION, the process generates IDs and indexes the data.
If you choose INDEXING, the process indexes the data without generating IDs.
Sourcepub fn build(self) -> Result<RuleBasedProperties, BuildError>
pub fn build(self) -> Result<RuleBasedProperties, BuildError>
Consumes the builder and constructs a RuleBasedProperties.
This method will fail if any of the following fields are not set:
Trait Implementations§
Source§impl Clone for RuleBasedPropertiesBuilder
impl Clone for RuleBasedPropertiesBuilder
Source§fn clone(&self) -> RuleBasedPropertiesBuilder
fn clone(&self) -> RuleBasedPropertiesBuilder
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Debug for RuleBasedPropertiesBuilder
impl Debug for RuleBasedPropertiesBuilder
Source§impl Default for RuleBasedPropertiesBuilder
impl Default for RuleBasedPropertiesBuilder
Source§fn default() -> RuleBasedPropertiesBuilder
fn default() -> RuleBasedPropertiesBuilder
impl StructuralPartialEq for RuleBasedPropertiesBuilder
Auto Trait Implementations§
impl Freeze for RuleBasedPropertiesBuilder
impl RefUnwindSafe for RuleBasedPropertiesBuilder
impl Send for RuleBasedPropertiesBuilder
impl Sync for RuleBasedPropertiesBuilder
impl Unpin for RuleBasedPropertiesBuilder
impl UnwindSafe for RuleBasedPropertiesBuilder
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);