fix: correct return type of getDefaultReactSlashMenuItems to include key

[ysds]

Summary

Fix incorrect return type of getDefaultReactSlashMenuItems() to properly include the key property.

Rationale

Items returned by getDefaultReactSlashMenuItems() actually contain a key property (inherited from getDefaultSlashMenuItems()), but the return type DefaultReactSuggestionItem[] omits key. This causes type errors when users try to access item.key:

getDefaultReactSlashMenuItems(editor).filter((item) => {
  console.log(item.key); // Error: Property 'key' does not exist
});

Changes

• Updated return type of getDefaultReactSlashMenuItems() to include key property
• Simplified return type of getPageBreakReactSlashMenuItems() by removing unnecessary Omit

Impact

• Users can now access item.key without type errors
• No breaking changes to runtime behavior

Testing

• Type checking passes for all packages

Screenshots/Video

N/A (type-only change)

Checklist

• Code follows the project's coding standards.
• Unit tests covering the new feature have been added.
• All existing tests pass.
• The documentation has been updated to reflect the new feature

Additional Notes

[vercel]

@ysds is attempting to deploy a commit to the TypeCell Team on Vercel.

A member of the Team first needs to authorize it.

[nperez0111]

I don't think this is correct right? Aren't you marking all of the items as having a page_break key, when that is not actually the case. Shouldn't you change DefaultReactSuggestionItem instead?

[ysds]

Thanks for taking a look. I’ll check it out.

[ysds]

To clarify, Omit<Dictionary["slash_menu"], "page_break"> here represents "a union of keys excluding page_break", not "marking items as having a page_break key". This pattern follows the same approach used in the DefaultSuggestionItem.ts

I believe the current implementation is correct, but I do agree that modifying DefaultReactSuggestionItem could be a better approach.

However, changing DefaultReactSuggestionItem requires a deeper understanding of BlockNote's design decisions. The key property was removed from DefaultReactSuggestionItem in #652, but the PR doesn't explain why. I can only speculate on the reasons:

• Potential conflicts with React's key prop
• Custom suggestion items may not need a key

Making changes to DefaultReactSuggestionItem feels beyond my current understanding of the codebase. This PR at least addresses the immediate type issue.