Close Stale PRs
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.5k
- Forks
- 456
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
All of these PRs look like they are going nowhere.
Maybe we can close them and ask the authors to resubmit if they are still into the idea?
- Adds two new doc events: 'before op batch' and 'after op batch' #247 opened on Sep 13, 2018 by danburzo
- Sync presence and undo redo #229 opened on Jul 20, 2018 by gkubisa
- Implement undo/redo enhancement #216 opened on Jun 21, 2018 by gkubisa
- Do not compose
createwithop#213 opened on Jun 12, 2018 by gkubisa - Sync ephemeral presence data enhancement #207 opened on Apr 26, 2018 by gkubisa
- Fix hasWritePending in op's callback #205 opened on Apr 24, 2018 by gkubisa
- Emit error on failed resubscribe #174 opened on Oct 17, 2017 by gkubisa
- [Proposal] Op Event Changes #129 opened on Oct 8, 2016 by roark
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the current status and discussion of the eight pull requests listed in issue #398, including #247, #229, #216, #213, #207, #205, #174, and #129. Confirm which are still inactive, then close the agreed stale PRs and ask their authors to resubmit if they still want the changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100