Single instance of changesReader expands to one per follow
- Dominant language
- JavaScript
- Stars
- 689
- Forks
- 167
- Avg merge
- 1h
- Merged PRs (30d)
- 1
Description
The `v11` change is causing me to rethink separately instantiating `changesReader` instances myself, so that I can have one per `follow` of a particular changes stream.
Putting this issue here as a possible point to contribute an alternative behavior for `changesReader` or factory of `changesReader` instances.
Would be great to be able to remove my now-outdated fork of `changesReader` by itself, outside `nano` proper!
Contributor guide
Research direction
Start by reading the current changesReader implementation and the v11 change that prompted this issue. Clarify whether the desired behavior belongs in changesReader itself or in a factory, and define how separate instances should behave for each follow so the external fork can be removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100