-
Notifications
You must be signed in to change notification settings - Fork 115
LIVE-784 Sell and Fund flow #2232
base: develop
Are you sure you want to change the base?
Conversation
Is this supposed to still be a draft @JunichiSugiura ? If not, you have failing CI (unused imports and whatnot) and should fill all the description so I know what this is about 🙏🏼 |
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.
I was not able to run and test these changes locally on my computer due to unrelated S1 performance issues / throttling
const exchangeAction = createAction(completeExchange); | ||
const sendAction = txCreateAction(connectApp); | ||
|
||
const styles = StyleSheet.create({ | ||
root: { | ||
flex: 1, | ||
padding: 32, | ||
}, | ||
}); |
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.
Couldn't we move the definition of these variables before the declaration of the PlatformCompleteExchange
function (l 23) to follow the no-use-before-define rule and therefore reduce confusion?
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.
To me the most important part of the file is its props and functional component and these should be defined at the top most. It's the same reason as defining styles in the bottom. If you think no-use-before-define
rule is the best bet, then it should be forced by a linter. Forcing without linter would become unmanageable eventually.
const action = createAction(connectApp, startExchange); | ||
|
||
const styles = StyleSheet.create({ | ||
root: { | ||
flex: 1, | ||
padding: 32, | ||
}, | ||
}); |
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.
Couldn't we move the definition of these variables before the declaration of the PlatformStartExchange
function (l 18) to follow the no-use-before-define rule and therefore reduce confusion?
@JunichiSugiura FYI I updated the test plan section in the description to reference the platform-app-test-exchange app and add info regarding the test version of the nano |
Type
Feature
Context
LIVE-784
It's the same as LedgerHQ/ledger-live-desktop#4361 but for mobile.
Parts of the app affected / Test plan
PS: You will need a test version of the exchange app to test the fund flow, cf. the platform-app-test-exchange README for details.
.env
manifest.json
fund-flow.mov