Change of current internal object store to allow for relation mappings instead of current indexable container implementation
I'm not sure if I got it right, can you illustrate somehow the current behavior and your proposal?
Read full answer below ↓Question
What are you trying to add to GrapesJS? Currently newly instantiated editor instances are added to a indexable collection where the user must manage the relationship of these editors in their implementation. Instead there should be a managed collection where the user can provide a key value which will then be mapped to the instance of the editor. This will also allow for an extension of the Editor API to add CRUD API endpoints to manage object instances.
Is there an alternative at the latest version? Not currently
Is this related to an issue? No
Answers (4)
I'm not sure if I got it right, can you illustrate somehow the current behavior and your proposal?
Basically, I am looking for a change of the exposed list that aggregates the editor instances on initialization so changing editors from a list to a map with a new property on the init configuration object in the resemblance of editorInstanceId I can create a poc in the up coming days.
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we ne...
Thanks for reporting this, @jlong-crestron. Great suggestion about FEAT: Change of current internal object store to allow for relation mappings instead of current indexable container implementation! While this specific feature isn't yet in the core API, there are several ways to achieve similar beh...
Related Questions and Answers
Continue research with similar issue discussions.
Issue #3496
FEAT: Mark Component as Dirty
What are you trying to add to GrapesJS? Component should be able to mark themselves as dirty, triggering the onbeforeunload warning message...
Issue #3215
Content loading issues from remote database
Hi, I created Grapejs Pagebuilder. I have two links one for pagebuilder1 and another for PAgeBuilder2. Both are redirected to grpaejs edito...
Issue #3525
FEAT: In Style Manager, Allow Requiring the Default Setting
What are you trying to add to GrapesJS? The CSS property float only makes sense for position: static; elements, which happens to be the def...
Issue #4607
JS error when moving an element with its child
GrapesJS version[x] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v104Reproducible demo link https://gr...
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.
Tutorial
Super Tooltip for GrapesJS — Version 0.1.5 Released 🎉
We’re excited to announce the v 0.1.5 update of Super Tooltip, our floating‑menu and tooltip plugin for GrapesJS
Tutorial
GrapesJS in 2026: The Complete Guide to the Open-Source Web Builder Framework
Master GrapesJS in 2026. Architecture, code examples, React integration, plugin development, Studio SDK, and how it compares to other projects
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.