brianegan/flutter_architecture_samples

How to use 'web_socket_channel' in todos_repository_simple

Open

#159 opened on Nov 14, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Dart (8,920 stars) (1,717 forks)batch import
good first issue

Description

Web socket as data Provider

todos_repository_simple explains nicely about the benefits of using repository as singleton. But no where it's mentioned how to handle the web sockets.

How can I use web socket (webSocket and fileStorage) instead of rest (webClient and fileStorage) ?

Some key points between web socket and rest.

  • The name itself signify socket is stateLess and rest is stateFull
  • socket is bidirectional : Server can send data to client and client will have a callback to perform accordingly and vice versa.

My dataProvider is socket and fileStorage and follows flutter_bloc architecture.

Every time we receive data from socket : Article : reload the UI directly in widget by mapping switch case. Flutter_bloc: need to reload the UI through bloc_state.

Thanks.

Contributor guide

Tech stack
dartflutter
Domain
mobile
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Flutter basicsRepository patternWebSocket concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue asks how to integrate web socket channel into the todos repository simple pattern. The repository currently uses REST (webClient) and fileStorage. To answer, investigate the existing repository pattern, then explore how web sockets can replace REST for real time updates, possibly using Streams in Dart. No linked PRs or recent activity; the maintainer may need to provide guidance or propose adding an example.