ipfs/ipfs-companion

Switch API polling to ipfs-stats

Open

#358 opened on Jan 20, 2018

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (1,992 stars) (364 forks)batch import
P3good first issuehelp wantedkind/maintenancestatus/deferred

Description

Background

Right now we poll stats about peers and repo manually. @hacdias extracted similar code into ipfs-stats during his work on IPFS Desktop 👌

It may be a good idea to reuse it in Companion to decrease code we have to maintain..

References

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
refactor
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.
half day
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
familiarity with IPFS Companion codebaseunderstanding of current polling mechanismknowledge of npm package integration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue suggests replacing manual API polling for peers and repo stats with the `hacdias/ipfs stats` package, as done in IPFS Desktop (PR #595). Investigate the current polling implementation in the IPFS Companion codebase (likely in background scripts), and integrate `ipfs stats` as a dependency. Ensure to update any related tests and remove the existing manual polling code. The linked PR and package provide examples of the integration.