-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Conversation
app={ app } | ||
availability={ availability } | ||
className={ styles.dapp } | ||
key={ `${index}_${app.id}` } |
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.
Wouldn't app.id be enough?
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, overkill (as I typed it that thought came to mind)
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.
Actually no. Just "fixed", the "reverted" as I remembered why I took this longer route.
When I have the app as both a local app (linked from dapps) as well as an app of the network, the ids are the same. (It was not an issue previously since they were in separate lists)
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 makes sense.
js/src/Dapps/dapps.js
Outdated
@@ -48,6 +46,7 @@ class Dapps extends Component { | |||
} | |||
|
|||
render () { | |||
const { availability } = this.props; | |||
let externalOverlay = null; | |||
|
|||
if (this.store.externalOverlayVisible) { |
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.
We could use a ? : operator here for externalOverlay
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.
Sure.
A start, there is more that can be done, provides a springboard for more cleanups.