Conversation
Rename all slashMenu references to contextMenu for consistency: - Rename extension dir/files: slash-menu/ → context-menu/ - Rename component dir/files: SlashMenu.vue → ContextMenu.vue - Update config keys: slashMenuConfig → contextMenuConfig - Update events: slashMenu:open/close → contextMenu:open/close - Update CSS classes: .slash-menu-* → .context-menu-* - Update exports, types, docs, and tests - Add backward-compat aliases with deprecation warnings
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7475b2c184
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -1 +0,0 @@ | |||
| export * from './slash-menu.js'; | |||
There was a problem hiding this comment.
Because @superdoc/super-editor still exports deep paths via exports["./*"] in package.json, removing extensions/slash-menu/index.js means existing consumers who import @superdoc/super-editor/extensions/slash-menu will now hit a module‑not‑found error at build/runtime. This is a breaking change for users relying on the old path, and it’s inconsistent with the new deprecation shims for slashMenu config and SlashMenu alias. Consider keeping a stub that re‑exports from context-menu (or adjusting the export map) to avoid breaking existing integrations.
Useful? React with 👍 / 👎.
1 participant
No description provided.