FEAT: Plugin Names
Question
Request that I be allowed to refer to plugins by two conventions: "grapesjs-lory-slider" and "grapesjsLorySlider".
I'm using a Kotlin JS DSL and it can't handle the dashes; also typically dashes are reserved for css class names and should be minimized in JS... though I suspect there is a class by that name, it should probably be decoupled from the JS object names to avoid confusion and help prevent unknown issues.
Answers (2)
I did find a solution this["grapesjs-lory-slider"], still recommended addition.
Honestly, I don't see any advantage in having 2 conventions. The name with dashes is generated by Webpack UMD bundler (eg. using grapesjs-cli) which is taken from the package.json name.
If we'll get more requests from the community and a proposed solution, I might reopen it.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #3163
FEAT: Shape Divider for GrapesJS
Is there grapedrop shape divider plugin for grapesjs? Is there a website that sells plugins for grapesjs?
Issue #2005
Invalid class names allowed
When adding a class name, the editor allows you to create class names that are invalid in CSS, but valid in HTML (e.g. 123). As adding clas...
Issue #2138
[BUG] Gradient plugin is interfering with background-image
The background-image url is getting wrapper around by linear-gradient() function like so Even though I assigned gradient to 'background' pr...
Issue #2750
Shared styles between pages
Hi, i want to have multiple pages whith shared styles. But when i'm switching between pages, it replaces not only components but also css r...
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.