Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Single instance of changesReader expands to one per follow #357

Copy link
Copy link
@digitalextremist

Description

@digitalextremist
Issue body actions

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.