New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Financial Connections] Compose support. #5117
[Financial Connections] Compose support. #5117
Conversation
…ial-connections-module # Conflicts: # financial-connections/build.gradle
Diffuse output:
APK
MANIFEST
DEX
ARSC
|
@Composable | ||
fun createComposable( | ||
callback: (FinancialConnectionsSheetResult) -> Unit | ||
): FinancialConnectionsSheet = FinancialConnectionsSheet( | ||
FinancialConnectionsSheetForDataLauncher( | ||
rememberLauncherForActivityResult( | ||
FinancialConnectionsSheetForDataContract() | ||
) { callback(it) } | ||
) | ||
) |
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.
Alternatively we could use the same naming we do in the Payments SDK. However, this is not the Compose naming convention when using the remember
API.
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.
This is really cool!
Should we also migrate |
bfe91c7
Summary
rememberFinancialConnectionsSheet
andrememberFinancialConnectionsSheetForToken
@composable functions.Why not on a different module?
SDK binary size would be a concern that could be solved by having a
financial-connections-compose
kind of module for integrators using Compose. However, we're planning on using Compose in the SDK as well so we're not seeing added value on an extra module.Motivation
Support Financial Connections in Jetpack Compose.
Screenshots
flow.mp4
Changelog