-
Notifications
You must be signed in to change notification settings - Fork 363
Fix: deep-linked tx – use current timestamp as fallback #3146
Conversation
CLA Assistant Lite All Contributors have signed the CLA. |
safeAddress, | ||
}), | ||
) | ||
history.push(txRoute) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Transaction deeplinking must be enabled to test this ticket. Whether we disabled it again after needs to be decided.
@@ -162,11 +162,13 @@ export const makeTxFromDetails = (txDetails: TransactionDetails): Transaction => | |||
? txDetails.detailedExecutionInfo | |||
: getMultisigExecutionInfo(txDetails) | |||
|
|||
// Will only be used as a fallback whilst waiting on backend tx creation cache | |||
const now = new Date().getTime() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
JFYI, there's a short version of the same: Date.now()
(w/o new).
ESLint Summary View Full Report
Report generated by eslint-plus-action |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Deployment links
|
E2E Tests Failed Failed tests:
|
Pull Request Test Coverage Report for Build 1555094727
💛 - Coveralls |
It looks good to me. The rejected tx in the history shows immediately in the correct date section |
What it solves
Resolves #3069
How this PR fixes it
Navigation to deeplinked transaction after transaction creation was enabled because the error was occurring with this feature. When a deeplinked transaction is opened, and hence loaded from backend via it's
txId
, the custom frontend-onlyTransaction
typed object is created.After the immediate creation of a transaction, the fetched transaction may lack a
timestamp
. As such, the fallback value was changed from0
to the current timestamp because the transaction was effectively created 'now'. Later polls for transactions will overwrite this with the exact timestamp that is eventually fetched.How to test it