-
Notifications
You must be signed in to change notification settings - Fork 741
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/aris/threads beta feedback #5647
Conversation
Unit Test Results110 files + 4 110 suites +4 1m 23s ⏱️ -3s Results for commit a269aa5. ± Comparison against base commit 08476a9. This pull request removes 2 and adds 9 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
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.
Some small remarks
to the users. | ||
--> | ||
|
||
<bool name="feature_threads_beta_feedback_enabled">true</bool> |
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.
Since this is a temporary flag, it's OK to keep it like that, but a FeatureFlag would have been better here. I am still writting the doc about it)
@@ -1648,6 +1648,10 @@ | |||
<string name="feedback_sent">Thanks, your feedback has been successfully sent</string> | |||
<string name="feedback_failed">The feedback failed to be sent (%s)</string> | |||
<string name="give_feedback">Give Feedback</string> | |||
<string name="give_feedback_threads">Give Feedback on threads</string> |
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.
F
-> f
?
<string name="give_feedback_threads">Give Feedback on threads</string> | |
<string name="give_feedback_threads">Give feedback on threads</string> |
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.
Its with capital "F" in the designs
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, but the current strategy is rather to avoid capitalization. Can you double check with the product please?
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.
They still want that with Capital F for that specific case, new string resource will be Give Feedback
instead of Give Feedback on threads
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.
ok, thanks for double checking.
ReportType.AUTO_UISI_SENDER, | ||
ReportType.AUTO_UISI -> bugDescription | ||
ReportType.AUTO_UISI -> bugDescription | ||
ReportType.THREADS_BETA_FEEDBACK -> "[Element] [threads-feedback] $bugDescription" |
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.
Not a blocker but I would have added this case just below SPACE_BETA_FEEDBACK
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.
Refactored!
@@ -350,6 +351,7 @@ class BugReporter @Inject constructor( | |||
builder.addFormDataPart("label", "android") | |||
builder.addFormDataPart("label", "uisi-sender") | |||
} | |||
ReportType.THREADS_BETA_FEEDBACK -> builder.addFormDataPart("label", "threads-feedback") |
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.
same remark about ordering cases
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.
Updated!
app:layout_constraintEnd_toEndOf="parent" | ||
android:background="@drawable/bg_shadow_divider" | ||
app:layout_constraintBottom_toTopOf="@id/threadsFeedBackConstraintLayout" | ||
/> |
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.
To avoid possible blink, it's better to hide those new views by default.
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.
In this case it's the opposite, to avoid blinking we should turn them on, they are not dynamic. Feedback will be on by default
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.
OK. But it's worth to see the View to quickly vanish when opening the screen (if the bool was set to false), than to see the View to quickly appear.
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 see your point, I have something in mind that will be a solution for both
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.
@bmarty A solution would be to use data binding conversions such as:
@BindingConversion
fun booleanToVisibility(visible: Boolean) = if(visible) View.VISIBLE else View.GONE
So then we will be able to do in our xml:
android:visibility="@{@bool/myBooleanFlag}"
However this requires to enable data binding for the whole project and introduces some boilerplate, so I will change the default to false !
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.
yeah, that does not worth it. Also in the XML config we could have view style, defining a visibility...
android:id="@+id/threadsFeedBackConstraintLayout" | ||
android:layout_width="0dp" | ||
android:layout_height="wrap_content" | ||
android:elevation="30dp" |
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.
Why do you need an elevation here?
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.
For the shadow, however I enhanced it by adding the divider view so we don't really need that
android:startColor="#00000000" | ||
android:endColor="#1A000000" | ||
/> | ||
</shape> |
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.
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.
Thanks for the update!
Type of change
Content
Users will be able to provide feedback for threads
Screenshots / GIFs
Closes #5452