[QUESTION] Reset trait on edit the content of a custom component

Hi,

I have a custom component which content can be changed by switching trait select options, but also can be edited similar to the text component type when it is already rendered inside the canvas. Is there an easy way to reset the traits related attribute on edit of a component?

model: {
        defaults:  {
         type: 'tag',
          tagName: 'span',
          droppable: 0,
          editable: 1,
          textable: 1,
          traits: [{
            type: 'select',
            label: 'Custom type',
            name: 'customType',
            options: customTypeOptions,
          }],
        },
		toHTML() {
          return this.get('content');
        },

view: {
	events: {
            focus: 'resetTrait',
	},
	reseTrait() {
	}
}

[inaLar]

@artf, regarding the “Select” I couldn’t manage to connect the change in the content and make it work on change of the trait in one flow and also to change it manually by editing it’s text/content. The manual change wasn’t syncing the trait, but I managed to make it work. A custom text component worked just fine.

As for the documentation from the last release, I am reading it right now and it looks very good, but I haven’t seen it when I posted the question.

It may be only me, but I learn by example, so more examples and use cases will be always a plus.

I understand that the product is open and I appreciate your effort. I hope that I will gain more knowledge and will be able to contribute with something in near future.

Cheers.

[artf]

Just one more thing - my trait is “Select”, so on marking the custom element in the canvas, the settings correspond to the current value of the components content. (this is working perfectly)

@inaLar I didn’t get the problem here

And maybe the documentation is more difficult for me to use.

Yes I agree, @artf could use a bit of work on the docs to provide a byte of better explanations and use cases.

In the last release, I rewrote the Trait documentation from scratch (and added new API for customization) by trying to cover all the possible needs requested so far by GrapesJS users (doing the same right now for Components). Obviously, I can’t cover all cases for all the people but if you have any suggestion are more than welcome