Skip to content
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: [lw-11786] rely on network infor provider for connectivity issues #1510

Merged
merged 7 commits into from
Nov 8, 2024

Conversation

vetalcore
Copy link
Contributor

@vetalcore vetalcore commented Nov 1, 2024

Checklist

  • JIRA - LW-11786
  • Proper tests implemented
  • Screenshots added.

Proposed solution

Explain how does this PR solves the problem stated in JIRA ticket.
You can also enumerate different alternatives considered while approaching this task.

Testing

Describe here, how the new implementation can be tested.
Provide link or briefly describe User Acceptance Criteria/Tests that need to be met

Screenshots

Attach screenshots here if implementation involves some UI changes

@vetalcore vetalcore self-assigned this Nov 1, 2024
@vetalcore vetalcore requested a review from a team as a code owner November 1, 2024 12:42
@pczeglik-iohk
Copy link
Contributor

pczeglik-iohk commented Nov 1, 2024

Allure Report

allure-report-publisher generated test report!

processReports: ✅ test report for 004e22c6

passed failed skipped flaky total result
Total 32 0 4 0 36

setNetworkConnection(isConnected ? NetworkConnectionStates.CONNNECTED : NetworkConnectionStates.OFFLINE);
let isNetworkInfoProviderConnected = true;
if (type === MessageTypes.NETWORK_INFO_PROVIDER_CONNECTION) {
isNetworkInfoProviderConnected = (data as HTTPConnectionStatus).connected;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you type the structure so the as syntax isn't required?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done here c9311d6

@vetalcore vetalcore force-pushed the fix/lw-11786-handle-network-errors branch 2 times, most recently from 2e4f624 to eaddf0a Compare November 5, 2024 11:12
@vetalcore vetalcore force-pushed the fix/lw-11786-handle-network-errors branch 3 times, most recently from 249fe24 to 1b3c244 Compare November 7, 2024 13:02
@vetalcore vetalcore force-pushed the fix/lw-11786-handle-network-errors branch from 1b3c244 to 004e22c Compare November 8, 2024 12:28
Copy link

sonarcloud bot commented Nov 8, 2024

@vetalcore vetalcore merged commit 7268732 into main Nov 8, 2024
29 checks passed
@vetalcore vetalcore deleted the fix/lw-11786-handle-network-errors branch November 8, 2024 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants