-
Notifications
You must be signed in to change notification settings - Fork 23
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
fix(settings): update channel details #2022
Conversation
82abf35
to
9b72158
Compare
/> | ||
<Section | ||
name={t('is_ready')} | ||
testID={channel.is_channel_ready ? 'IsReadyYes' : 'IsReadyNo'} |
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.
IsReadyYes is checked in e2e tests
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 it's ok to remove the test since it's only checking if the row exists. For debugging is_channel_ready
hasn't really been useful so far
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.
If we are removing is_channel_ready from tests, than we need to add is_usable 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.
The test was only checking if the row exists, now it will exist always (without developer mode on) so I don't see the point of testing this. @limpbrains thoughts?
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 just the row. Test was checking if LDK api return channel.is_channel_ready
9b72158
to
9141484
Compare
Description
Type of change
Tests
Screenshot / Video