-
Notifications
You must be signed in to change notification settings - Fork 22
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/CV2-5785: media dialog view ux updates to include media match reason #2256
base: epic/CV2-5510-why-media-is-in-cluster
Are you sure you want to change the base?
Conversation
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.
looking good @danielevalverde
i just made some small tweaks mostly about being explicit and using "cluster of media"
instead of just cluster in some places
@@ -42,10 +42,10 @@ const getIconAndMessage = (type, user) => { | |||
), | |||
tooltipMessage: ( | |||
<FormattedHTMLMessage | |||
defaultMessage="<strong>{user}</strong> uploaded this media using the Check interface" | |||
defaultMessage="<strong>{media_cluster_origin_user}</strong> uploaded this media using the Check interface" |
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 would change slightly from:
...using the Check interface
to
...using Check
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.
✅
@@ -61,10 +61,10 @@ const getIconAndMessage = (type, user) => { | |||
), | |||
tooltipMessage: ( | |||
<FormattedHTMLMessage | |||
defaultMessage="<strong>{user}</strong> added this media by merging from another cluster" | |||
defaultMessage="<strong>{media_cluster_origin_user}</strong> added this media by merging from another cluster" |
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.
please change from
...merging from another cluster
to
...merging from another cluster of media
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.
✅
@@ -51,10 +53,10 @@ const getIconAndMessage = (type, user, cluster, timestamp) => { | |||
message: ( | |||
<> | |||
<FormattedHTMLMessage | |||
defaultMessage="This media was added to the cluster by <strong>{user}</strong> when merged from <strong><u>{cluster}</u></strong> " | |||
description="Message for User Matched" | |||
defaultMessage="This media was merged to the cluster by <strong>{media_cluster_origin_user}</strong>, " |
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.
Please change from
This media was merged to the cluster by...
to
This media was merged into this cluster of media by...
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.
✅
@@ -66,10 +68,10 @@ const getIconAndMessage = (type, user, cluster, timestamp) => { | |||
message: ( | |||
<> | |||
<FormattedHTMLMessage | |||
defaultMessage="This media was added to the cluster by <strong>{user}</strong> when accepted from <strong><u>{cluster}</u></strong> " | |||
defaultMessage="This media was added to the cluster by <strong>{media_cluster_origin_confirmed_by}</strong> when accepted from <strong><u>{media_cluster_origin_title}</u></strong>, " |
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.
from
This media was added to the cluster by...
to
This media was added to the cluster of media by...
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.
✅
@@ -81,7 +83,7 @@ const getIconAndMessage = (type, user, cluster, timestamp) => { | |||
message: ( | |||
<> | |||
<FormattedHTMLMessage | |||
defaultMessage="This media was automatically matched to the cluster " | |||
defaultMessage="This media was automatically matched to the cluster, " |
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.
from
...matched to the cluster,...
to
...matched to the cluster of media,...
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.
✅
addressed the review comments 🫡 |
@@ -214,6 +215,14 @@ class MediaComponent extends Component { | |||
)]} | |||
/> | |||
} | |||
media_origin_banner={ |
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.
prop names should follow camelCase
=> mediaOriginBanner={
@@ -115,6 +115,10 @@ const MediaOriginBanner = ({ | |||
); | |||
}; | |||
|
|||
MediaOriginBanner.defaultProps = { | |||
media_cluster_relationship: {}, |
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.
prop names should follow camelCase
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.
Please change props that are passed with snake_case
to camelCase
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.
nice, thanks for that data fix @danielevalverde !
just one small UI nit to fix on my end:
- please add maybe 8px of space below the banner in the dialog, so its not right up against the media like in the screenshot here:
Description
Type of change
How has this been tested?
manually and running the unit tests
Things to pay attention to during code review
Checklist
propTypes
are declared and they use React Hooks and, if data-fetching is required, they use Relay Modern with fragment containers