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
[🔁] Cancel Pledge redesign #594
Conversation
@@ -42,12 +46,12 @@ class CancelPledgeFragment : BaseFragment<CancelPledgeViewModel.ViewModel>() { | |||
this.viewModel.outputs.showServerError() | |||
.compose(bindToLifecycle()) | |||
.compose(Transformers.observeForUI()) | |||
.subscribe { Snackbar.make(snackbar_anchor, R.string.Something_went_wrong_please_try_again, Snackbar.LENGTH_SHORT).show() } | |||
.subscribe { snackbar(cancel_pledge_root, getString(R.string.Something_went_wrong_please_try_again)).show() } |
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.
🍿
<3 functions as first class citizens in Kotlin! 🎆
"amount", amount, "project_name", name) | ||
|
||
val spannableString = SpannableString(formattedString) |
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.
Ah ok so at this point formatted string already has the data interpolated, and using SpannableString
is really just to add bold-ness to the string for the amount and name of the project, right?
I'm getting 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.
...I think
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.
yes!
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 looks great! Out of curiosity, what was the reason behind changing over to a BehaviorSubject
for progressBarIsVisible
and PublishSubject
for the showCancelError
and showServerError
? Does it have to do with the fact that we no longer have a close button on the new version of this screen?
(also apologies for the delay between making comments and approving, had to hop into a meeting)
Hey @oliverswitzer, np!! So, a Compared to a So you want to use a |
📲 What
Implementation of the cancel pledge redesign.
🤔 Why
Redesign™
🛠 How
ksr_grey_300
.BehaviorSubject
s that should've beenPublishSubject
s, you know how it goes.👀 See
📋 QA
Notes 2 u, the QA individual:
1️⃣ Tertiary (gray) buttons are
ksr_grey_400
and notksr_grey_500
so it does not match the Abstract.2️⃣ Outlined text fields do not have a fill. We can switch to the filled text fields if desired.
3️⃣ Regression test: you should still be able to cancel your pledge or dismiss the screen.
Story 📖
https://dripsprint.atlassian.net/browse/NT-200