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.

💬 Answered: Plugin Names

Answers (2)

gunslingor• August 24, 2020

I did find a solution this["grapesjs-lory-slider"], still recommended addition.

artf• August 28, 2020

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.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →

Premium option

Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.

Browse premium plugins →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.

Presets Plugins Components Blocks Assets Commands I18n Layers Styles Storages RTE Newsletters Web pages Site builders

Plugin Names

Question

Answers (2)

Related Questions and Answers

FEAT: Shape Divider for GrapesJS

When we resize an image with a class 'xyz', all the elements on the page with same class also gets resized because editor adds css to those classes.

FEAT: Disable Dragging

The grapesjs slider buttons, tabs are not working as expected

Paid Plugins That Match This Issue

Browse Plugin Categories