-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: configured/extended extensions should keep their original config #4191
Conversation
✅ Deploy Preview for tiptap-embed ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - this does not break any functionality while you tested it? @tleruitte
CC @svenadlung - you want to take another look?
@bdbch Sorry I missed your comment. No, I didn't see any broken functionality with this fix! |
@bdbch @svenadlung Let me know if there is anything else I can do to get this merged :) |
I'm wondering if this could be something released as |
I think this got fixed in 2.1.0 by another pull request. https://github.com/ueberdosis/tiptap/releases/tag/v2.1.0 |
Never mind, just tested |
I merged it for now and will release a new RC version with this tomorrow. Would be nice if someone could check it out by then |
This appears as fixed in Any idea why tiptap/packages/core/src/ExtensionManager.ts Lines 240 to 242 in 42039c0
Also maybe tiptap/packages/core/src/helpers/getSchemaByResolvedExtensions.ts Lines 145 to 163 in 42039c0
|
This commit causes #4617. See review comments. |
Please describe your changes
Extensions, marks and nodes should keep their original config when they are extended or configured.
How did you accomplish your changes
n/a.
How have you tested your changes
Tested locally.
How can we verify your changes
Before this fix, the instance of
Code
doesn't haveexcludes
,code
orexitable
set. This prevents the right arrow keyboard shortcut to exit the code mark for instance. After the fix, the config is correctly extended and the new instance ofCode
uses the correct values forexcludes
,code
orexitable
. Same goes forExtension
andNode
.Remarks
This is especially noticeable when users use the StarterKit. StarterKit configures all extensions with
undefined
by default, which strips them all from their default config.Checklist
Related issues
I haven't filed an issue.