Display correct shortcut for Strikethrough, depending on extension version #314
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This ensures the correct mod+Shift+S shortcut is displayed by default (used in newer versions of the strike extension package), but uses mod+Shift+X if the extension is configured to use that shortcut, for users still on Tiptap <2.1.0 (for backwards compatibility).
Alternative to the PR that just changes to mod+Shift+S by default #305, and would require users of Tiptap <2.1.0 to pass
<MenuButtonStrikethrough tooltipShortcutKeys={["mod", "Shift", "X"]} />
.