Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new keys for factor source slide ups #578

Merged
merged 3 commits into from
Jan 21, 2025
Merged

Conversation

micbakos-rdx
Copy link
Contributor

Keys for transactionReview and factorSourceActions

@micbakos-rdx micbakos-rdx self-assigned this Jan 20, 2025
"factorSourceActions_createKey_title": "Creating Key",
"factorSourceActions_device_messageSignature": "Authenticate to your phone to sign.",
"factorSourceActions_device_message": "Authenticate to your phone to complete using your phone's signing key.",
"factorSourceActions_device_signMessage": "Use your phone’s biometrics or PIN to sign",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is the factorSourceActions_device_messageSignature still required? Seems confusing to have messageSignature & signMessage

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to delete the keys, but we had discussed to not remove keys in the past. Are you ok to remove the old ones?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

given that we already need to update code after renaming _passphrase into offDeviceMnemonic, I believe it is a good time to delete them now

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also

  • factorSourceActions_ledger_messageSignature
  • factorSourceActions_ledger_messageDeriveAccounts
    will not be supported. Should we delete?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we delete, the still not removed UIs will not compile.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is fine, I can make a quick update on main to just use the new Strings (together with the other mentioned updates) and then on future PR update the entire UI

Comment on lines 25 to 29
"transactionReview_deletingAccount_message": "Deleting Account. Permanently removing access and preventing future deposits.",
"transactionReview_signingTransactionFailure_title": "Cannot Sign Transaction",
"transactionReview_signingTransactionFailure_message": "You’ve skipped too many factors and cannot sign the transaction. You can restart the signing process, or cancel it.",
"transactionReview_signingTransactionFailure_restart": "Restart Signing",
"transactionReview_signingTransactionFailure_cancel": "Cancel Transaction"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Being that these 4 are just the first of a lot of failure cases to implement, should we put them under a new Signing Failure folder?
So that it would have:
"signingFailure_transaction_XYZ" -> Strings for this screen
"signingFailure_shield_XYZ" -> Strings for this screen

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree

@micbakos-rdx micbakos-rdx merged commit 3ad88a7 into main Jan 21, 2025
@micbakos-rdx micbakos-rdx deleted the interactor-slide-ups branch January 21, 2025 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants