search

GrapesJS / grapesjs

Free and Open source Web Builder Framework. Next generation tool for building templates without coding
https://grapesjs.com
BSD 3-Clause "New" or "Revised" License
22.36k stars 4.05k forks source link

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

Closed jlong-crestron closed 3 years ago

jlong-crestron commented 3 years ago

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

artf commented 3 years ago

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

jlong-crestron commented 3 years ago

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] commented 3 years ago

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.