zec
/
secant-android-wallet
mirror of https://github.com/zcash/secant-android-wallet.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
secant-android-wallet/sdk-ext-lib/build.gradle.kts

41 lines
1.0 KiB
Plaintext
Raw Permalink Normal View History

[#28] Initial SDK integration This sets up the infrastructure needed to continue implementing the onboarding UI for create and import of wallets. By fleshing out the global state management in the app now, we can better manage asynchronous IO to avoid blocking the UI. This adds: - Load and persistence a wallet in encrypted preferences - The stored data is written as a single JSON object, as opposed to multiple entries, to ensure atomic writes - The data is versioned, so that we can change the JSON format readily in the future - Detection of application state, e.g. onboarding versus loading the user's wallet - Touch points to initialize the SDK
2021-11-12 04:09:30 -08:00
plugins {
id("com.android.library")
kotlin("android")
[#482] Rename build-convention to build-conventions-secant This prevents naming conflicts with included builds across multiple projects with build conventions.
2022-06-13 11:06:23 -07:00
id("secant.android-build-conventions")
[#433] Use emulator.wtf for tests on CI (#428) This should speed up our builds and reduce flakiness. Followup items: - Enable coverage - Collect screenshots - Fix target API on sdk-ext-lib #430
2022-05-17 07:06:56 -07:00
id("wtf.emulator.gradle")
[#482] Rename build-convention to build-conventions-secant This prevents naming conflicts with included builds across multiple projects with build conventions.
2022-06-13 11:06:23 -07:00
id("secant.emulator-wtf-conventions")
[#673] process .ec files from emulator.wtf Co-authored-by: Carter Jernigan <git@carterjernigan.com> Co-authored-by: Honza <rychnovsky.honza@gmail.com>
2023-02-13 05:10:32 -08:00
id("secant.jacoco-conventions")
[#28] Initial SDK integration This sets up the infrastructure needed to continue implementing the onboarding UI for create and import of wallets. By fleshing out the global state management in the app now, we can better manage asynchronous IO to avoid blocking the UI. This adds: - Load and persistence a wallet in encrypted preferences - The stored data is written as a single JSON object, as opposed to multiple entries, to ensure atomic writes - The data is versioned, so that we can change the JSON format readily in the future - Detection of application state, e.g. onboarding versus loading the user's wallet - Touch points to initialize the SDK
2021-11-12 04:09:30 -08:00
}
android {
[#586] AGP 7.3
2022-09-19 05:24:19 -07:00
namespace = "cash.z.ecc.sdk.ext"
[#28] Initial SDK integration This sets up the infrastructure needed to continue implementing the onboarding UI for create and import of wallets. By fleshing out the global state management in the app now, we can better manage asynchronous IO to avoid blocking the UI. This adds: - Load and persistence a wallet in encrypted preferences - The stored data is written as a single JSON object, as opposed to multiple entries, to ensure atomic writes - The data is versioned, so that we can change the JSON format readily in the future - Detection of application state, e.g. onboarding versus loading the user's wallet - Touch points to initialize the SDK
2021-11-12 04:09:30 -08:00
}
dependencies {
implementation(libs.kotlin.stdlib)
implementation(libs.kotlinx.coroutines.android)
implementation(libs.kotlinx.coroutines.core)
[#310] [Scaffold] Progress Status Circular Bar * [#310] [Scaffold] Progress Status Circular Bar - Added Z to Home ZECs balance - Added USD balance text to Home - Prepared Text extension functions for both - Provided Zatoshi to USD conversion methods + filed related SDK conversion issue * Update Home screen UI with progress bars - Implemented scaffolding UI of progress bars - Added related texts to strings * Update Home screen UI with progress bars - Connected some of the implemented UI elements to SDK values - Added app update information to Home screen - Update WalletSnapshot with progress field * Update Home screen UI with progress bars - Capturing and handling errors from SDK Synchronizer. - Added related error strings. - Simplified Home screen UI. * Zboto font added. Load it in runtime. Import to Typography. * Updated ZEC sign icon. * Draw ZEC balance with Zboto font * Simplify Home screen balances assigning * Switch to PercentDecimal progress representatiton * Support different locales while working with fiat currency * Fix bug in checking of fiat currency value * Generalize strings to provide possibility of other fiat currencies * Add fiat currency conversion states mechanism * Add TODO comment with reference to follow up SynchronizerError issue * Add WalletDisplayValues to simplify HomeView composable * Add CurrencyConversion class for connection to Price API (and convert Zatoshi to fiat currency) * Add basic HomeView tests * Add basic HomeViewIntegration test * Review changes - Used Duration API for times - Allow injecting clock into currency conversion - Moved FiatCurrencyConversionRateState to sdk-ext-ui because I suspect that we’ll consider this to be a UI object. I based this on the fact that current/stale cutoff values are arbitrary and probably should be the domain of the UI rather than the SDK. - Added some tests, although additional coverage is needed - Added fixtures for model objects * Minor code refactoring - Move UpdateInfoFixture class to fixture dir - Remove unnecessary annotation - Add common application context method to test suite - Fix Test class import - Move several WalletSnapshotFixture parameters to const fields * Add WalletDisplayValuesTest to cover the model class. * Fix import after changes merged * Use the new MonetarySeparatorsFixture in related tests * Add a few basic Zatoshi -> USD conversion tests * Turn on core lib desugaring for sdk-ext-ui-lib module * Make WalletDisplayValues a data class I think there may be some instances where this can help with recomposition * Add preference key for fiat currency This allows us to configure reading the value with observers correctly, even if we don’t allow the user to change it right now. * Delegate symbol and formatting to JVM * Add tests for Locale Co-authored-by: Carter Jernigan <git@carterjernigan.com>
2022-07-13 00:16:05 -07:00
implementation(libs.kotlinx.datetime)
[#142] Send ZEC scaffold (#253) Implements a basic scaffold for sending ZEC. Some new model objects and an extension method were added that I hope to move to the SDK. Followup issues include - Press-and-hold for the Send button #249 - Prevent illegal input in input form #218 - Prevent undefined behavior if locale changes #217 - Add error handling to the Zec send screen #250 - Add confirmation after send is created #252
2022-03-01 05:11:23 -08:00
api(libs.zcash.sdk)
[#757] Adopt SDK 1.14.0 (#759)
2023-02-17 03:05:23 -08:00
api(libs.zcash.sdk.incubator)
[#142] Send ZEC scaffold (#253) Implements a basic scaffold for sending ZEC. Some new model objects and an extension method were added that I hope to move to the SDK. Followup issues include - Press-and-hold for the Send button #249 - Prevent illegal input in input form #218 - Prevent undefined behavior if locale changes #217 - Add error handling to the Zec send screen #250 - Add confirmation after send is created #252
2022-03-01 05:11:23 -08:00
api(libs.zcash.bip39)
[#28] Initial SDK integration This sets up the infrastructure needed to continue implementing the onboarding UI for create and import of wallets. By fleshing out the global state management in the app now, we can better manage asynchronous IO to avoid blocking the UI. This adds: - Load and persistence a wallet in encrypted preferences - The stored data is written as a single JSON object, as opposed to multiple entries, to ensure atomic writes - The data is versioned, so that we can change the JSON format readily in the future - Detection of application state, e.g. onboarding versus loading the user's wallet - Touch points to initialize the SDK
2021-11-12 04:09:30 -08:00
androidTestImplementation(libs.bundles.androidx.test)
[#62] Wallet details scaffold Implements a details screen showing various wallet addresses Some known issues requiring followup in future pull requests: - #159 Colors for light theme have not been defined yet - #160 Color blocks have 2x borders along the top/bottom of the middle item - #161 Some address types display placeholder values
2021-12-31 05:28:16 -08:00
androidTestImplementation(libs.kotlinx.coroutines.test)
[#135] Request ZEC scaffold
2022-02-17 05:08:06 -08:00
androidTestImplementation(libs.kotlin.test)
[#28] Initial SDK integration This sets up the infrastructure needed to continue implementing the onboarding UI for create and import of wallets. By fleshing out the global state management in the app now, we can better manage asynchronous IO to avoid blocking the UI. This adds: - Load and persistence a wallet in encrypted preferences - The stored data is written as a single JSON object, as opposed to multiple entries, to ensure atomic writes - The data is versioned, so that we can change the JSON format readily in the future - Detection of application state, e.g. onboarding versus loading the user's wallet - Touch points to initialize the SDK
2021-11-12 04:09:30 -08:00
[#592] Instrumentation coverage Co-authored-by: Carter Jernigan <git@carterjernigan.com>
2023-01-17 11:54:40 -08:00
androidTestUtil(libs.androidx.test.services) {
artifact {
type = "apk"
}
}
[#28] Initial SDK integration This sets up the infrastructure needed to continue implementing the onboarding UI for create and import of wallets. By fleshing out the global state management in the app now, we can better manage asynchronous IO to avoid blocking the UI. This adds: - Load and persistence a wallet in encrypted preferences - The stored data is written as a single JSON object, as opposed to multiple entries, to ensure atomic writes - The data is versioned, so that we can change the JSON format readily in the future - Detection of application state, e.g. onboarding versus loading the user's wallet - Touch points to initialize the SDK
2021-11-12 04:09:30 -08:00
if (project.property("IS_USE_TEST_ORCHESTRATOR").toString().toBoolean()) {
androidTestUtil(libs.androidx.test.orchestrator) {
artifact {
type = "apk"
}
}
}
}