fix: Check code
mark presence instead of any mark in canInsertSuggestion
#791
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.
Overview
This PR addresses an issue in the
canInsertSuggestion
function where it was incorrectly checking for the presence of any mark in the node before the selection, rather than specifically checking for acode
mark. The fix ensures that the function now verifies the existence of acode
mark before determining if a suggestion can be inserted.References
PR Checklist
Test plan
Rich-text → Default
story**bold**
(yes, that's a space character at the end)@
@
@