-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feature: top up screen (kids-843) #763
Conversation
@@ -77,13 +78,67 @@ class ChildDetailsCubit extends Cubit<ChildDetailsState> { | |||
} | |||
} | |||
|
|||
Future<void> topUp(int amount) async { | |||
await _logTopUpEvent(amount); |
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.
Small thing. Personally i would not "await" analytics event. So I would always wrap them in unawaited(); My reasoning is we wouldn't want to wait on analytics in the user experience and if analytics fail its not blocking for the app.
@@ -15,6 +15,10 @@ final class ChildDetailsFetchingState extends ChildDetailsState { | |||
const ChildDetailsFetchingState(); | |||
} | |||
|
|||
final class ChildTupUpFundsErrorState extends ChildDetailsState { |
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.
tupup => topup
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.
Very good, you apply learnings very fast and you split up future tickets nicely 👍
Description