- snapshot package added
- welcome snapshot taken
[337] Set up Snapshot Testing
- iPhone 8 Plus welcome screen references
[337] Set up Snapshot Testing
- snapshot references removed
- snapshots only recorded, no comparison
[337] Set up Snapshot Testing
- isRecording removed
[337] Set up Snapshot Testing
- iPhone 8 Plus, iOS 15.4 screenshots
[337] Set up Snapshot Testing
- lowering the precision to 0.999
[337] Set up Snapshot Testing
- attempts to get it pass the test
[337] Set up Snapshot Testing
- frame set up
[337] Set up Snapshot Testing
- resized image
[337] Set up Snapshot Testing
- many different snapshot tests
[337] Set up Snapshot Testing
- low precision test
[337] Set up Snapshot Testing
- updated pngs
[337] Set up Snapshot Testing
- another set of pngs
[337] Set up Snapshot Testing
- precision 0.99
[337] Set up Snapshot Testing
- XCTAttachments
[337] Set up Snapshot Testing
- typo fixed
[337] Set up Snapshot Testing
- reference images
[337] Set up Snapshot Testing
- no precision set
[337] Set up Snapshot Testing
- screenshot names added
- precision so low it passes all the time
[337] Set up Snapshot Testing (350)
- cleanup
[337] Set up Snapshot Testing (350)
- removed snapshot library completely
[337] Set up Snapshot Testing (350)
- code simplification and cleanup
[337] Set up Snapshot Testing (350)
- adding attachments refactored to simplify the code even more
[337] Set up Snapshot Testing (350)
- last simplification to wrap both light and dark under the hood
[337] Set up Snapshot Testing (350)
- addAttachments method to follow the same XCTestCase terminology
[337] Set up Snapshot Testing (350)
- attachments name fix
- recovery phrase randomizer & wrapper
- did finish launching -> initialized wallet test
- cleanup of static dependencies
- did finish launching -> keys missing integration test
- did finish launching -> uninitialized integration test
- database files were missing, mocked to behave like it's available
- key missing test fix, the database files were missing too => mocked to act like being present
- Int64+Zcash.swift and Double+Zcash.swift removed
- Balances and amounts updated to use Zatoshi
- Remove TODOs
- Tests updated
- FIXED: Send amount being in Zatoshi is clamping $ value to 21M max -> send amount input is no longer Zatoshi typed
[329] Update wallet to use Zatoshi type (333)
- alphabetical order(s)
[329] Update wallet to use Zatoshi type (333)
- static .zero for the Zatoshi
- conformance to Equatable moved to extension
[329] Update wallet to use Zatoshi type (333)
- small improvement by reducing code duplicity
- added words counter X/24
- added input for the birthday
- all kinds of validity check implemented
- unit tests for the whole import wallet business logic implemented
[301] Import Wallet does not have a Birthday input field (328)
- support for the birthday to be optional input
[301] Import Wallet does not have a Birthday input field (328)
- Int -> BlockHeight refactor
- scan UI view
- UI representable
- scaffold of scan view
- rect of interest support
- simple URI parser and validator
- tests
[106] [Scaffold] Scan QR Screen
- scan status added
- scan status tests
[106] [Scaffold] Scan QR Screen
- custom back button added
[106] [Scaffold] Scan QR Screen
- fixed typo
[106] [Scaffold] Scan QR Screen (321)
- valid vs. invalid code part of the enum
[106] [Scaffold] Scan QR Screen (321)
- refactor
[106] [Scaffold] Scan QR Screen (321)
- cleanup
[106] [Scaffold] Scan QR Screen (321)
- review comments solved
- some improvements added
- firing the valid qr code after 1s
[106] [Scaffold] Scan QR Screen (321)
- tests fixed
- onAppear test added
- print() cleanup
[106] [Scaffold] Scan QR Screen (321)
- wrapped audio services
- vibrate when QR found
- alphabetical order of environmental parameters
- AVCaptureSession stopRunning explicit call, probably handled by AVCaptureSession itself but I didn't find proof
- QRCodeScanView simplified and cleaned up
[106] [Scaffold] Scan QR Screen (321)
- URIParser added to the project
[#306] Release build is broken because placeholder is not compiled
[#215] Warning: Non-constant range: argument must be an integer literal
Fix comment spacing warning
Closes#258
this checks that when the user taps the finished button on the phrase displayed it has definitely not passed the test before going to the recovery flow.
Note: this should actually go to the next or previous screen according to the context.
That should be taken into consideration when implementing the profile screen that takes the user to the phrase diplay screen from that context.
Add //TODO comment with the permanent fix for the problem