Is it possible to save and load "traits" separately from the HTML?

[bryanjamesmiller]

Hi @artf - happy greetings! We are running into an issue which is requiring us to save and load the HTML via html string format when we initialize the Grapes editor. However, we are noticing that when our users add their own custom traits (as we allow them to do this on the fly), the HTML (and Grapes object) saves the trait fine, but then the next time the Grapes editor loads, the trait manager menu on the right sidebar doesn't load the custom trait the user created from the HTML in string format mentioned above.

When we initialize Grapes using the saved Javascript object instead of the HTML string, then our user-added traits load fine in the trait manager/sidebar. However, since we need to load the editor content using the HTML string, it seems what we really need is to be able to save and load the custom trait data in the trait manager sidebar separately from the HTML if possible somehow. Is this currently possible? Can you think of any ideas to help us here? Ideally it would be like:

grapesjs.init({
    // typical stuff, but we have to use the HTML string to initialize the content
    components: savedHtmlString,

    // These have a set of built-in traits that work fine already 
    blocks: ourBlocks,

    // This is the feature request here, where we can set additional traits our users create on the fly.  
    // These traits would get added on top of the set of built-in traits that already load fine mentioned above, 
    // but only for the particular block they were created on.
    additionalTraits: userAddedTraits,  
})

Thank you!!

[bryanjamesmiller]

Just as an update to this one, we did find a way around this for now, so feel free to disregard :) Thanks!