Component has a dash in API docs
Yeah, the intention was to emphasize it being under the DOM Components module but seems like I failed 😬
Read full answer below ↓Question
In API docs, the component header is prepended by a dash. Not sure if that's on purpose.
Answers (2)
Yeah, the intention was to emphasize it being under the DOM Components module but seems like I failed 😬
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #1843
Class on different states are not being applied to those states.
I'm trying to apply a class on hover of a component and the class is being applied but not on hover, it applies with normal state. Please l...
Issue #1695
Adding new trait to Video component
I want to add a new trait for existing VIDEO '' component. I follow the docs and I didn't find what I want. Now I got the new trait added t...
Issue #362
How to create custom link components that prompts users to type link/choose link similar to Images Component Modal
Image Components have logic to call Modal and prompt user's interaction for options/configuration of image url. Would like to do similar to...
Issue #987
[BUG/Question] Dropdown indicator not displayed for a custom trait
Hello, the dropdown (select) element arrow indicator icon is not rendered when adding a custom trait to a component: I'm using following co...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.
Browse premium plugins →Related tutorials
In-depth guides on the same topic.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.