Give Feedback About Connection State

Open
#581 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
frontend, networking

Research direction

Start by reviewing issue 525 and locating the current websocket disconnect logging path. The work is done when disconnect state is shown to users in a lower-right message queue, disappears after some time, and the lifecycle messaging is configurable for different clients.

Written by the indexing model from the issue text.

Description

priority-3-low
Current Situation

Presently, if connection to a websocket is lost we log to the console. This is fine for debugging purposes, but for users it could be frustrating if the page simply stops working for what would seem like no apparent reason.

Proposed Actions

When a websocket disconnects we should add a model to the lower right of the screen explaining as much which will disappear after some time. What exactly is should should be configurable though so that different clients are able to hook into the Websocket's life-cycle events. Doing this would also address similar proposals.

Work Items
Dominant language
Python
Stars
8.1k
Forks
332
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from reactive-python/reactpy

All issues in reactive-python/reactpy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.