[BUG]: Two command names (new and old) cause the command division.
Question
For some predefined commands, has a new name and old name. It tells the user to use the new one as preferred. If choosing the new command name to extend, will not works, that because of old names in the internal.
The reason is: In commands/index.js, the added or extended commands are the newly created views (extends from CommandAbstract).
Here is my code snippet, it not works if the defaultCommand option value is select-comp
const Command = editor.Commands.get('core:component-select')
editor.Commands.extend('core:component-select', {
// Overwrite this private method to make the toolbar conditionally display.
updateToolbar(mod) {
...
Command.updateToolbar.call(this, mod)
}
})
Answers (0)
No answers yet.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #3267
BUG: Cannot set 0px box shadow blur
For some reason, the editor does not allow to set the blur to 0px. 0 always magically turns into 5px. <img width="243" alt="Screenshot 2021...
Issue #2824
Dragging items do not position on intital drag?
So when I drag a component/item from the bar to the center it will not go where I told it to go... IT always goes about 20% page width to o...
Issue #1092
[BUG]traits and storage trigger
Hey, maybe it's not bug, i'm not sure. I have traits with changeProp: true field. When I change the value of trait by UI, model is changed...
Issue #2697
[QUESTION] Problem with custom component type and table cell
Hello! I'm trying to add custom component type: And also I'm adding new block: But when I drop this block on the canvas the <td> tag doesn'...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.