Rendering virtual DOM in prosemirror.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 39
- Avg merge
- 21h 40m
- Merged PRs (30d)
- 15
Description
Implementing complex Vue components in the editor may cause some glitch effect.
It tried many times digging into prosekit and prosemirror to found a workaround but without success.
I stubbed upon this blog post. The guy explain deeply the problem, and he describes the same issue of my mine !
https://smoores.dev/post/why_i_rebuilt_prosemirror_view/#:~:text=Depending%20on%20how,the%20first%20keypress!
Here's the source of his fork :
https://github.com/handlewithcarecollective/react-prosemirror
It's quite hard to me to implement this feature in prosekit. I don't know enough prosekit in deep :/
I think maybe with a custom node view factory...
Have you got any tips to start implanting their solution ?
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 linked blog post and react-prosemirror fork, then compare their approach with Prosekit and ProseMirror, including the suggested custom node view factory. Reproduce the Vue-component glitch and establish a concrete rendering behavior and verification steps before treating the work as complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100