Issue #3193Opened December 18, 2020by jlong-crestron0 reactions

FEAT: Change of current internal object store to allow for relation mappings instead of current indexable container implementation

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 (3)

artfDecember 30, 20200 reactions

I'm not sure if I got it right, can you illustrate somehow the current behavior and your proposal?

jlong-crestronDecember 30, 20200 reactions

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.

no-response[bot]January 10, 20210 reactions

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 need so that we can investigate further.

Related Questions and Answers

Continue research with similar issue discussions.

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...

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.