Closed ofreyssinet-ledger closed 2 years ago
[x] src/components/BottomModal.js
[x] src/components/Button.js
[x] src/components/CurrencyRate.js
[x] src/components/DiscreetModeButton.js
[x] src/components/GenericErrorView.js
[x] src/components/LText/index.js
[x] src/components/OperationRow.js
[x] src/components/RequiresBLE/BluetoothDisabled.js
[x] src/components/RootNavigator/MainNavigator.js
[x] src/components/RootNavigator/ManagerNavigator.js
[x] src/components/SelectDevice/BluetoothEmpty.js
[x] src/components/SelectDevice/index.js
[x] src/components/TabIcon.js
[x] src/screens/Account/index.js
[x] src/screens/Onboarding/steps/deviceSelection.js
[x] src/screens/Onboarding/steps/language.js
[x] src/screens/Onboarding/steps/welcome.js
[x] src/screens/PairDevices/Scanning.js
[x] src/screens/Portfolio/Header.js
[x] src/screens/Settings/Debug/index.js
[x] src/screens/Settings/General/LanguageRow.js
[x] src/screens/Settings/General/ThemeSettingsRow.js
[x] src/screens/Settings/General/index.js
[x] src/screens/makeGenericSelectScreen.js
Fixes:
<OpenDebugEnv />
). (cf. https://github.com/LedgerHQ/ledger-live-mobile/pull/2172)<Scanning />
pair device screen: (cf. https://github.com/LedgerHQ/ledger-live-mobile/pull/2017.)GenericErrorView
-> this view should check the bluetooth permission in case the error is an instance ofBluetoothRequired
. (cf. https://github.com/LedgerHQ/ledger-live-mobile/pull/2131)OperationRow
, the NFT name was not being rendered for NFT operations.More context for this PR:
I made a script in
scripts/v3check.js
for the purpose of comparing git history between JS files and their TS/TSX counterpart.Basically it checks the creation date of a tsx file (e.g.
filename.ts|tsx
) and lists all the commits that happened since that date on the corresponding file (filename.js
). It then generates a markdown string with a TODO list, that you can see in the following comment on this PR.This allows us to detect changes that might have been done on one side in
develop
and might not have been included in the rebranding files (the typescript ones).The script is quite rudimentary so it might not catch everything but it caught two of the regressions that we already identified before (regression on the "region setting" feature https://github.com/LedgerHQ/ledger-live-mobile/pull/2332 and regression on some fixes on the discreet mode https://github.com/LedgerHQ/ledger-live-mobile/pull/2365 ).
On top of that as you can see in the following list it helped me to catch some other regressions (Upon checking each commit in the list one by one, I then added for the π¨ emoji whenever I found a regression) that happened because of the branching between js and ts files.
I'm pushing the script to the repo even though it will probably not be used anymore on LLM, but it might be useful for the pre-release of the LLD rebranding. Eventually we can delete it.
Type
Regression fixes
Context
v3 pre-release
Parts of the app affected / Test plan