Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 3 commits
- 112 files changed
- 2 contributors
Commits on Aug 15, 2024
-
fix(react): attempt to cleanup editor instances, on creation #5492 (#…
…5496) The core of the change ended up being quite simple, because we can create the editor within the first render, we need to already schedule it's destruction. Scheduling a destruction, ensures that an instance that was created in that first render pass can be cleaned up. Waiting one more tick than before ensures that we don't accidentally destroy an editor instance that could actually be valid in the next render pass. In StrictMode, there will be two editor instances created, the first will be created & quickly destroyed in 2 ticks. In Normal React, there will only ever be 1 instance created and destroyed only on unmount.
-
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff @tiptap/core@2.6.3...@tiptap/core@2.6.4