Add a comment about the interaction between CardTransaction::init_card_caps and CardTransaction::initialize
This commit is contained in:
parent
a85d3164d7
commit
629eecd510
1 changed files with 5 additions and 1 deletions
|
@ -70,7 +70,11 @@ pub trait CardTransaction {
|
||||||
/// Set the card capabilities in the CardTransaction.
|
/// Set the card capabilities in the CardTransaction.
|
||||||
///
|
///
|
||||||
/// Setting these capabilities is typically part of a bootstrapping
|
/// Setting these capabilities is typically part of a bootstrapping
|
||||||
/// process: the information about the card's capabilities is typically
|
/// process (this fn is typically called from [CardTransaction::initialize].
|
||||||
|
/// When implementing CardTransaction, you probably want to call
|
||||||
|
/// [CardTransaction::initialize] during setup).
|
||||||
|
///
|
||||||
|
/// The information about the card's capabilities is typically
|
||||||
/// requested from the card using the same CardTransaction instance,
|
/// requested from the card using the same CardTransaction instance,
|
||||||
/// before the card's capabilities have been initialized.
|
/// before the card's capabilities have been initialized.
|
||||||
fn init_card_caps(&mut self, caps: CardCaps);
|
fn init_card_caps(&mut self, caps: CardCaps);
|
||||||
|
|
Loading…
Reference in a new issue