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

Feature/UI indicate when no connection #10774

Merged
merged 5 commits into from
Jun 22, 2022

Conversation

p0psicles
Copy link
Contributor

@p0psicles p0psicles commented Jun 22, 2022

  • PR is based on the DEVELOP branch
  • Don't send big changes all at once. Split up big PRs into multiple smaller PRs that are easier to manage and review
  • Read the contribution guide

Add a small indicator (red cross) to the Medusa log in the top left, for when medusa has no connection to the apiv2 or the websocket.

Modified the behavior of the icon, in that when a connection is lost, clicking on it will reload the whole page. Instead of routing to /#

Implement #10761

* Have it reload the page instead of routing to home.
* Extend the retries for the socket connection to 25 x 2500 ms.
@p0psicles p0psicles added this to the 1.0.4 milestone Jun 22, 2022
@p0psicles p0psicles merged commit 5eabc60 into develop Jun 22, 2022
@p0psicles p0psicles deleted the feature/ui-indicate-when-no-connection branch June 22, 2022 12:54
@@ -9,7 +9,11 @@
<span class="icon-bar" />
<span class="icon-bar" />
</button>
<app-link class="navbar-brand" href="home/" title="Medusa"><img alt="Medusa" src="images/medusa.png" style="height: 50px;" class="img-responsive pull-left"></app-link>
<app-link v-if="isConnected || !socketIsConnected" class="navbar-brand" style="position: relative" title="Medusa">
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't this supposed to be !isConnected?

Right now I always get a disconnected icon and so clicking on the logo refreshes the page.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I fixed that in a PR that came after

Copy link
Contributor

Choose a reason for hiding this comment

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

Was broken on my end. Had the fixed version, but my Synology Reverse Proxy didn't forward it correctly without some additional config.

https://mlohr.com/websockets-for-synology-dsm/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants