Skip to content
This repository has been archived by the owner on Jul 15, 2022. It is now read-only.

Algorand #799

Merged
merged 23 commits into from Aug 13, 2020
Merged

Algorand #799

merged 23 commits into from Aug 13, 2020

Conversation

henri-ly
Copy link
Contributor

@henri-ly henri-ly commented Jul 31, 2020

The PR is still not mergeable, we are still missing :

@vercel
Copy link

vercel bot commented Jul 31, 2020

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/ledgerhq/ledger-live-common/ky12u3u76
✅ Preview: https://ledger-live-co-git-fork-ledger-coin-integration-team-alg-f5d729.ledgerhq.vercel.app

Copy link
Contributor

@gre gre left a comment

Choose a reason for hiding this comment

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

some feedback on different places. my main feedback is to finish the work done in the specs.js, at least we should improve the bot tests because dataset.js feels pretty light at the moment in term of coverage (one account, some txs).

For the bot i feel we should have at least covered:

  • sending assets
  • validation of text on the device
  • claimReward (with some invariant on exactly what "selects" a claim reward tx candidate, like from a certain available amount – see cosmos)

a bit less prio but still recommended would also to cover:

  • memo
  • opt out only if it's technically easy to add: even if it's not part of Live UI, i feel the bot needs it for the duality of actually being able to test opt in 🤔

src/families/algorand/bridge/libcore.js Outdated Show resolved Hide resolved
src/families/algorand/bridge/libcore.js Outdated Show resolved Hide resolved
src/families/algorand/bridge/libcore.js Outdated Show resolved Hide resolved
src/families/algorand/bridge/libcore.js Outdated Show resolved Hide resolved
@@ -0,0 +1,151 @@
/********************************************************************************
Copy link
Contributor

Choose a reason for hiding this comment

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

is there plan to contribute back to ledgerjs repo?

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 don't think so, but it can be, but I don't know what the requirement to be in ledgerjs repo ? what the minimum functionalities we do need ?

Copy link
Contributor

Choose a reason for hiding this comment

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

i can deal with it after it's merged, but basically we should make a @ledgerhq/hw-app-algorand with what you have so the community can reuse / contribute.

src/families/algorand/specs.js Outdated Show resolved Hide resolved
src/families/algorand/specs.js Outdated Show resolved Hide resolved
src/families/algorand/specs.js Outdated Show resolved Hide resolved
src/families/algorand/tokens.js Show resolved Hide resolved
src/libcore/platforms/nodejs.js Show resolved Hide resolved
src/env.js Outdated Show resolved Hide resolved
Copy link
Contributor

@gre gre left a comment

Choose a reason for hiding this comment

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

did we test on mobile? I have strong suspicion there will be bugs, at least with this present feedbacks

src/families/algorand/libcore-buildSubAccounts.js Outdated Show resolved Hide resolved
@gre gre self-assigned this Aug 13, 2020
@gre gre merged commit c242c37 into LedgerHQ:master Aug 13, 2020
@ghost ghost deleted the algorand-rebase branch June 4, 2021 09:26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants