Evaluate new invalid content detection option of tiptap
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
Tiptap introduced a new option in https://github.com/ueberdosis/tiptap/releases/tag/v2.9.0 to "disable transactions that are trying to sync invalid content" in collaboration.
We should check if it makes sense for us to introduce this option and handle this scenario with an error or reconnect or in some other way.
Upstream PR https://github.com/ueberdosis/tiptap/pull/5207
Contributor guide
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
Start by reading the Tiptap v2.9.0 release note and upstream PR #5207, then inspect this repository's collaboration integration to see how invalid content synchronization currently behaves. Done means agreeing on whether to enable the option and defining the expected error, reconnect, or alternative behavior, with the relevant implementation and verification work identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- distributed-systems, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100