pub struct AccountCapabilityFutureRequirements {
pub alternatives: Option<Vec<AccountRequirementsAlternative>>,
pub current_deadline: Option<Timestamp>,
pub currently_due: Vec<String>,
pub disabled_reason: Option<AccountCapabilityFutureRequirementsDisabledReason>,
pub errors: Vec<AccountRequirementsError>,
pub eventually_due: Vec<String>,
pub past_due: Vec<String>,
pub pending_verification: Vec<String>,
}Fields§
§alternatives: Option<Vec<AccountRequirementsAlternative>>Fields that are due and can be resolved by providing the corresponding alternative fields instead.
Multiple alternatives can reference the same original_fields_due.
When this happens, any of these alternatives can serve as a pathway for attempting to resolve the fields.
Additionally, providing original_fields_due again also serves as a pathway for attempting to resolve the fields.
current_deadline: Option<Timestamp>Date on which future_requirements becomes the main requirements hash and future_requirements becomes empty.
After the transition, currently_due requirements may immediately become past_due, but the account may also be given a grace period depending on the capability’s enablement state prior to transitioning.
currently_due: Vec<String>Fields that need to be resolved to keep the capability enabled.
If not resolved by future_requirements[current_deadline], these fields will transition to the main requirements hash.
disabled_reason: Option<AccountCapabilityFutureRequirementsDisabledReason>This is typed as an enum for consistency with requirements.disabled_reason, but it safe to assume future_requirements.disabled_reason is null because fields in future_requirements will never disable the account.
errors: Vec<AccountRequirementsError>Details about validation and verification failures for due requirements that must be resolved.
eventually_due: Vec<String>Fields you must collect when all thresholds are reached.
As they become required, they appear in currently_due as well.
past_due: Vec<String>Fields that haven’t been resolved by requirements.current_deadline.
These fields need to be resolved to enable the capability on the account.
future_requirements.past_due is a subset of requirements.past_due.
pending_verification: Vec<String>Fields that are being reviewed, or might become required depending on the results of a review.
If the review fails, these fields can move to eventually_due, currently_due, past_due or alternatives.
Fields might appear in eventually_due, currently_due, past_due or alternatives and in pending_verification if one verification fails but another is still pending.
Trait Implementations§
Source§impl Clone for AccountCapabilityFutureRequirements
impl Clone for AccountCapabilityFutureRequirements
Source§fn clone(&self) -> AccountCapabilityFutureRequirements
fn clone(&self) -> AccountCapabilityFutureRequirements
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more