[Question]: Editable components in Handlebars rendered template

Hi, I've been using grapes for about a couple of days now. Thanks for the awesome work on this project. I've read through the API docs (hopefully didn't miss this piece) and I've also tried some stuff out. Basically, I'm using grapes to load existing .hbs (handlebars) files in that the user will then be able to edit. I saw a previous question regarding how to integrate handlebars in #938 and I followed the advice there and ended up with.

   var comps = this.grapesEditor.DomComponents;

    // Get the model and the view from the default Component type
    var defaultType = comps.getType('default');
    var defaultModel = defaultType.model;
    var defaultView = defaultType.view;

    comps.addType('handlebars', {
        model: defaultModel.extend({
              defaults: Object.assign({}, defaultModel.prototype.defaults, {
                droppable: true,
                editable: true
              })
            }),
      view: defaultType.view.extend({
        // The render() should return 'this'
        render: function () {
          // Extend the original render method
          defaultType.view.prototype.render.apply(this, arguments);
          const template = Handlebars.compile(this.el.innerHTML);
          this.el.innerHTML = template();
          return this
        },
      }),
    });

And then setting the components on the editor like so:

      this.grapesEditor.setComponents({
        type: 'handlebars',
        content: fileData
      });

This works very well and I end up with my rendered handlebars template being shown in the editor with the source html remaining as handlebars template which is exactly what I need. However when the template gets brought in, it comes in as a single component in the layer manager called Handlebars, meaning I cannot edit individual elements or add anything new.

This makes perfect sense when reading the docs and considering that components are just atomic pieces that comprise building blocks. That being said, i'm not sure how to go about making it so that

• I can bring in an existing snippet of handlebars code
• Render the handlebars template in the edtior
• Keep the source code of the handlebars template
• Have the individual elements of the rendered handlebars template be editable in the grapes editor

I see that passing the uncompiled handlebars HTML string directly to editor.setComponents() does work in getting me editable components but obviously doesn't give me a rendered handlebars template. On the other hand, passing the compiled handlebars HTML template string in the same way to editor.setComponents() does work in giving me individually editable components from the compiled handlebars template, but changes the source html (to the compiled html).

I will continue to investigate and read through some samples / trying some things out, but I'm curious if its possible to do this with a custom component somehow.