Handle case where client sends update request when they have pending contracts. It should check the pending pool for the wallet metadata first and update based on that or proceed normally.
[x] Add pending pool map to HandleAccountInfoRequest
[x] In HandleAccountInfoRequest, first check if var walletAddress is a key in the pending pool map. If it is, the accInfo struct should be populated with the walletAddress, pending balance, and pending state nonce. Otherwise, it should proceed as it is already implemented.
[x] Add the pendingLock as a parameter, just like in HandleContractRequest
[x] Surround the section that uses the pending pool map with Lock and Unlock calls.
[x] Add a test case that supports a scenario with an account info request to an account that is present in the passed in pending pool map
[x] Refactor any usages in the repository of HandleAccountInfoRequest
kastolars
commented
5 years ago
Handle case where client sends update request when they have pending contracts. It should check the pending pool for the wallet metadata first and update based on that or proceed normally.
HandleAccountInfoRequestHandleAccountInfoRequest, first check ifvar walletAddressis a key in the pending pool map. If it is, theaccInfostruct should be populated with thewalletAddress, pending balance, and pending state nonce. Otherwise, it should proceed as it is already implemented.pendingLockas a parameter, just like inHandleContractRequestLockandUnlockcalls.HandleAccountInfoRequest